Sanitize qnx4 fsync handling
* have directory operations use mark_buffer_dirty_inode(),
so that sync_mapping_buffers() would get those.
* make qnx4_write_inode() honour its last argument.
* get rid of insane copies of very ancient "walk the indirect blocks"
in qnx4/fsync - they never matched the actual fs layout and, fortunately,
never'd been called. Again, all this junk is not needed; ->fsync()
should just do sync_mapping_buffers + sync_inode (and if we implement
block allocation for qnx4, we'll need to use mark_buffer_dirty_inode()
for extent blocks)
Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk>
Showing
- fs/qnx4/Makefile 1 addition, 1 deletionfs/qnx4/Makefile
- fs/qnx4/dir.c 1 addition, 1 deletionfs/qnx4/dir.c
- fs/qnx4/file.c 1 addition, 1 deletionfs/qnx4/file.c
- fs/qnx4/fsync.c 0 additions, 169 deletionsfs/qnx4/fsync.c
- fs/qnx4/inode.c 12 additions, 26 deletionsfs/qnx4/inode.c
- fs/qnx4/namei.c 2 additions, 2 deletionsfs/qnx4/namei.c
- include/linux/qnx4_fs.h 0 additions, 2 deletionsinclude/linux/qnx4_fs.h
Loading
Please register or sign in to comment