> > And so I strongly suggest this patch as well. Apparently this feature > > is not even used by anybody, otherwise somebody would have noticed > > when Trond's fix broke execute permission checking on regular files... > > And I'm very strongly against this. > If you wanted to rip out the resource inode logic, it would be more than > this. > At worst this code does nothing right now, so why this sudden rush to > remove this without even an attempt of fixing it? Because a) it's nontrivial to fix (even understanding the problem is nontrivial, see Documentation/filesystems/directory-locking) b) the feature is obviously unused, so the easiest fix is simply to remove it for the time being. We generally don't leave code around which is known to be deadlockable by unprivileged users. Of course if you have a better fix, then that's fine. Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
