> > > You have processes that don't react to signals, because some > > > other user land task is misbehaving. I'd call that ugly at the > > > very least. > > > > It already happens with, say, NFS. Don't think about it in terms of a > > userland task misbehaving - think of it in terms of a resource becoming > > unavailable. > > I think there's a difference between a userland task playing the role of a > resource and a "real" external resource the kernel doesn't control. > > IMO, userland tasks should not have the power to affect each other as though > they were parts of the kernel.
One task doing ptrace() can basically do whatever it wants with the task being traced. This is not an exact analogy to what fuse does, but close. And for this reason the security model for allowing access to a fuse filesystem is similar to that for allowing tracing. The gory details can be found in Documentation/filesystems/fuse.txt. Miklos - 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/
