Re: [PATCH v2 resend] vfs: new O_NODE open flag
From: Alan Cox
Date: Thu Nov 05 2009 - 08:15:00 EST
> - re-opening normally after checking file type (there's a debate
> whether this would have security issues, but currently we do allow
> re-opening with increased permissions thorugh /proc/*/fd)
Which has already been demonstrated to be an (unfixed) security hole.
> Filesystems which want to install special file operations for O_NODE
> opens (e.g. ioctl) may set S_OPEN_NODE flag in the inode. This will
Wrong way around. The defailt should be that O_NODE fails for any handle
which has not specifically added support.
It'll fill itself in where it matters pretty fast that way but cases will
get reviewed which is critical.
You also need to address the open with no permissions pinning a removable
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/