![]() FAT has the ATTR_RO (read-only) attribute. But on Windows, the ATTR_RO of the directory will be just ignored actually, and is used by only applications as flag. E.g. it's setted for the customized folder by Explorer. http://msdn2.microsoft.com/en-us/library/aa969337.aspx This adds "rodir" option. If user specified it, ATTR_RO is used as read-only flag even if it's the directory. Otherwise, inode->i_mode is not used to hold ATTR_RO (i.e. fat_mode_can_save_ro() returns 0). Signed-off-by: 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> |
||
---|---|---|
.. | ||
configfs | ||
00-INDEX | ||
9p.txt | ||
adfs.txt | ||
affs.txt | ||
afs.txt | ||
autofs4-mount-control.txt | ||
automount-support.txt | ||
befs.txt | ||
bfs.txt | ||
cifs.txt | ||
coda.txt | ||
cramfs.txt | ||
dentry-locking.txt | ||
directory-locking | ||
dlmfs.txt | ||
dnotify.txt | ||
ecryptfs.txt | ||
Exporting | ||
ext2.txt | ||
ext3.txt | ||
ext4.txt | ||
fiemap.txt | ||
files.txt | ||
fuse.txt | ||
gfs2-glocks.txt | ||
gfs2.txt | ||
hfs.txt | ||
hfsplus.txt | ||
hpfs.txt | ||
inotify.txt | ||
isofs.txt | ||
jfs.txt | ||
Locking | ||
locks.txt | ||
mandatory-locking.txt | ||
ncpfs.txt | ||
nfs-rdma.txt | ||
nfsroot.txt | ||
ntfs.txt | ||
ocfs2.txt | ||
omfs.txt | ||
porting | ||
proc.txt | ||
quota.txt | ||
ramfs-rootfs-initramfs.txt | ||
relay.txt | ||
romfs.txt | ||
rpc-cache.txt | ||
seq_file.txt | ||
sharedsubtree.txt | ||
smbfs.txt | ||
spufs.txt | ||
sysfs-pci.txt | ||
sysfs.txt | ||
sysv-fs.txt | ||
tmpfs.txt | ||
ubifs.txt | ||
udf.txt | ||
ufs.txt | ||
vfat.txt | ||
vfs.txt | ||
xfs.txt | ||
xip.txt |