summaryrefslogtreecommitdiffstats
path: root/drivers/connector/cn_proc.c
diff options
context:
space:
mode:
authorJan Engelhardt <jengelh@computergmbh.de>2008-02-06 01:36:08 -0800
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2008-02-06 10:40:59 -0800
commit19c561a60ffe52df88dd63de0bff480ca094efe4 (patch)
treeda1df4ab0a15434f81e4c1eaf021a486bcbea97e /drivers/connector/cn_proc.c
parent20292bc2c3feaee7f2e93911ffcb692732293894 (diff)
downloadlinux-19c561a60ffe52df88dd63de0bff480ca094efe4.tar.bz2
fs/fat/: refine chmod checks
Prohibit mode changes in non-quiet mode that cannot be stored reliably with the on-disk format. Suppose a vfat filesystem is mounted with umask=0 and [not-quiet]. Then all files will have mode 0777. Trying to change the owner will fail, because fat does not know about owners or groups. chmod 0770, on the other hand, will succeed, even though fat does not know about the permission triplet [user/group/other]. So this patch changes fat's not-quiet behavior so that only UNIX modes are accepted that can be mapped lossless between the fat disk format and the local system. There is only one attribute, and that is the readonly attribute, which is mapped to the UNIX write permission bit(s). chmod 0555 is therefore valid (taking away the +w bits <=> setting the readonly attribute). Since chmod 0775 and chmod 0755 is an ambiguous case as to whether to set or clear the readonly bit, these modes are also denied. In quiet mode, chmod and chown will continue to "succeed" as they did before, meaning that a subsequent stat() will temporarily return the new mode as long as the inode is not reread from disk, and chown will silently do nothing, not even return the new uid/gid in stat(). Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de> Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/connector/cn_proc.c')
0 files changed, 0 insertions, 0 deletions