lisa/android_kernel_xiaomi_sm8350
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

minix: fix bug when opening a file with O_DIRECT

Browse Source 
[ Upstream commit 9ce3c0d26c42d279b6c378a03cd6a61d828f19ca ]

Testcase:
1. create a minix file system and mount it
2. open a file on the file system with O_RDWR|O_CREAT|O_TRUNC|O_DIRECT
3. open fails with -EINVAL but leaves an empty file behind. All other
   open() failures don't leave the failed open files behind.

It is hard to check the direct_IO op before creating the inode.  Just as
ext4 and btrfs do, this patch will resolve the issue by allowing to
create the file with O_DIRECT but returning error when writing the file.

Link: https://lkml.kernel.org/r/20220107133626.413379-1-qhjin.dev@gmail.com
Signed-off-by: Qinghua Jin <qhjin.dev@gmail.com>
Reported-by: Colin Ian King <colin.king@intel.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
Qinghua Jin 2022-03-23 16:06:23 -07:00 committed by Greg Kroah-Hartman
parent a95bbfea8f
commit f4e16d12bc
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
fs/minix/inode.c
View File

@ -447,7 +447,8 @@ static const struct address_space_operations minix_aops = {
.writepage = minix_writepage, .writepage = minix_writepage,
.write_begin = minix_write_begin, .write_begin = minix_write_begin,
.write_end = generic_write_end, .write_end = generic_write_end,
.bmap = minix_bmap .bmap = minix_bmap,
.direct_IO = noop_direct_IO
}; };
static const struct inode_operations minix_symlink_inode_operations = { static const struct inode_operations minix_symlink_inode_operations = {