remarkable-linux/fs/ufs
Al Viro 4e3911f3d7 ufs: the offsets ufs_block_to_path() puts into array are not sector_t
type makes no sense - those are indices in block number arrays, not
block numbers.  And no, UFS is not likely to grow indirect blocks with
4Gpointers in them...

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2015-07-06 17:39:31 -04:00
..
balloc.c ufs: don't use lock_ufs() for block pointers tree protection 2015-07-06 17:39:25 -04:00
cylinder.c
dir.c ufs: use dir_pages instead of ufs_dir_pages() 2015-06-23 18:02:01 -04:00
file.c make new_sync_{read,write}() static 2015-04-11 22:29:40 -04:00
ialloc.c fs/ufs: restore s_lock mutex 2015-06-16 02:07:38 -04:00
inode.c ufs: the offsets ufs_block_to_path() puts into array are not sector_t 2015-07-06 17:39:31 -04:00
Kconfig
Makefile ufs: move truncate code into inode.c 2015-07-06 17:39:30 -04:00
namei.c Merge branch 'for-linus' into for-next 2015-06-17 14:44:05 -04:00
super.c ufs: kill lock_ufs() 2015-07-06 17:39:26 -04:00
swab.h
symlink.c ufs: switch to simple_follow_link() 2015-05-10 22:18:25 -04:00
ufs.h ufs: move truncate code into inode.c 2015-07-06 17:39:30 -04:00
ufs_fs.h
util.c
util.h