From: Lizhi Xu <lizhi.xu@windriver.com>
To: <syzbot+e36cc3297bd3afd25e19@syzkaller.appspotmail.com>
Cc: <almaz.alexandrovich@paragon-software.com>, <brauner@kernel.org>,
<jack@suse.cz>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <ntfs3@lists.linux.dev>,
<syzkaller-bugs@googlegroups.com>, <viro@zeniv.linux.org.uk>
Subject: [PATCH] fs/ntfs3: Add missing direct_IO in ntfs_aops_cmpr
Date: Fri, 11 Apr 2025 09:24:27 +0800 [thread overview]
Message-ID: <20250411012428.3473333-1-lizhi.xu@windriver.com> (raw)
In-Reply-To: <67f818d3.050a0220.355867.000d.GAE@google.com>
The ntfs3 can use the page cache directly, so its address_space_operations
need direct_IO.
Fixes: b432163ebd15 ("fs/ntfs3: Update inode->i_mapping->a_ops on compression state")
Reported-by: syzbot+e36cc3297bd3afd25e19@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=e36cc3297bd3afd25e19
Signed-off-by: Lizhi Xu <lizhi.xu@windriver.com>
---
fs/ntfs3/inode.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
index 3e2957a1e360..50524f573d3a 100644
--- a/fs/ntfs3/inode.c
+++ b/fs/ntfs3/inode.c
@@ -2068,5 +2068,6 @@ const struct address_space_operations ntfs_aops_cmpr = {
.read_folio = ntfs_read_folio,
.readahead = ntfs_readahead,
.dirty_folio = block_dirty_folio,
+ .direct_IO = ntfs_direct_IO,
};
// clang-format on
--
2.43.0
next prev parent reply other threads:[~2025-04-11 1:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 19:15 [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in generic_file_read_iter syzbot
2025-04-11 0:51 ` [syzbot] " syzbot
2025-04-11 1:24 ` Lizhi Xu [this message]
2025-04-14 5:50 ` [PATCH] fs/ntfs3: Add missing direct_IO in ntfs_aops_cmpr Christoph Hellwig
2025-04-15 1:05 ` Lizhi Xu
2025-04-15 9:05 ` Jan Kara
2025-04-15 9:26 ` [PATCH V2] " Lizhi Xu
2025-04-15 11:08 ` Jan Kara
2025-04-16 4:37 ` Christoph Hellwig
2025-04-16 5:34 ` Lizhi Xu
2025-04-16 5:35 ` Christoph Hellwig
2025-04-16 6:03 ` Lizhi Xu
2025-04-16 6:05 ` Christoph Hellwig
2025-04-16 6:18 ` Lizhi Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250411012428.3473333-1-lizhi.xu@windriver.com \
--to=lizhi.xu@windriver.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+e36cc3297bd3afd25e19@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.