> "Reparse points" or filters could be even more easily (and perhaps
> more fruitfully) implemented as part of the standard library.
It is amazing how the sub-file issues resemble sub-process issues.
Threads could be more easily implemented as part of libc, but
performance and correctness would suffer.
> This introduces another directory access on every open (to
> see if a directory has an .albod entry and hence should be treated
> as a file) even for non-albod aware apps. This might be a noticeable
> performance hit for certain apps.
No kidding. You won't use this. I won't use this. Nobody will use this.
I think you are proposing "solutions" to brush away the problem.
> Other advantages of a user-space implementation are fewer
> security concerns and portability to other OSs.
Fewer security concerns? When a setuid app runs a user-space filter...
(and it must, since the system won't work otherwise)
> However, the above directory structure wouldn't allow a file to
> impersonate a directory.
There goes the correctness.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/