mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-18 02:32:25 -04:00
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Make sure we check the truncate constraints early on in ->setattr by adding those checks to inode_change_ok. Also clean up and document inode_change_ok to make this obvious. As a fallout we don't have to call inode_newsize_ok from simple_setsize and simplify it down to a truncate_setsize which doesn't return an error. This simplifies a lot of setattr implementations and means we use truncate_setsize almost everywhere. Get rid of fat_setsize now that it's trivial and mark ext2_setsize static to make the calling convention obvious. Keep the inode_newsize_ok in vmtruncate for now as all callers need an audit for its removal anyway. Note: setattr code in ecryptfs doesn't call inode_change_ok at all and needs a deeper audit, but that is left for later. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> |
||
| .. | ||
| adfs.h | ||
| dir.c | ||
| dir_f.c | ||
| dir_f.h | ||
| dir_fplus.c | ||
| dir_fplus.h | ||
| file.c | ||
| inode.c | ||
| Kconfig | ||
| Makefile | ||
| map.c | ||
| super.c | ||