Andrew Morton wrote:
> Anssi Hannula <[email protected]> wrote:
>
>>>Generally we use file descriptors (and driver-specific state at
>>
>> > file.f_private) to manage things like that. But I'd imagine that we
>> > couldn't retain the existing semantics with any such scheme.
>> >
>> > A pragmatic approach would be to put a big fat comment in there explaining
>> > how it all works and leave it at that.
>>
>> As I don't see this could break any existing applications, I would very
>> much like to change the behaviour so that the effects are file
>> descriptor specific.
>
>
> ooh, that's always risky - we just don't know what people are doing out
> there. They do the damnedest things.
>
> Is it possible to implement the new behaviour while retaining the old
> behaviour as well? And to detect when an app is using the old behaviour
> and to drop a printk("stop doing this")? So we can kill the old behaviour
> in a year or so?
I *really* don't think any app is trying to do one of the following:
- open another fd to the same device and delete effect created in the
first fd
- open and close another fd to the same device to delete all effects
The latter one doesn't make any sense (the process could just open and
close the first fd), but the former one is possible, though very unlikely.
I count only 6 programs using linux ff, of which 3 are test programs.
None of those messes up with fd's so that they would depend on the old
behaviour. I would change the behaviour, while we still can.
What we could do is allow deleting effects, whether they're owned by the
fd or not. If they aren't, printk() would be issued.
>
>>What should I use to differentiate the descriptors?
>> Can I just compare the "struct file*"? (it seems to work well, I just
>> modified the code so)
>
> Depends what you're trying to do. Different threads in the same process
> can share the same file*'s.
I try to have a coherent behaviour:
- fd1 opened
- fd1: effects 0, 1 are created
- fd2 opened
- fd2: effects 2, 3 are created
- fd2 closed
=> effects 2, 3 get deleted
- fd1 uses effects
- fd1 closed
=> effects 0, 1 get deleted
I will once again give an example how things would go with the old
behaviour:
- fd1 opened
- fd1: effects 0, 1 are created
- fd2 opened
- fd2: effects 2, 3 are created
- fd2 closed
=> effects 0, 1, 2, 3 get deleted
- fd1 uses effects
=> failure
- fd1 closed
(fd1 and fd2 are of the same process and the same device)
--
Anssi Hannula
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
