From: syzbot <syzbot+e36cc3297bd3afd25e19@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in generic_file_read_iter
Date: Thu, 10 Apr 2025 17:51:42 -0700 [thread overview]
Message-ID: <67f8679e.050a0220.355867.0018.GAE@google.com> (raw)
In-Reply-To: <67f818d3.050a0220.355867.000d.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in generic_file_read_iter
Author: lizhi.xu@windriver.com
missing direct io func.
#syz test
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
next prev parent reply other threads:[~2025-04-11 0:51 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 [this message]
2025-04-11 1:24 ` [PATCH] fs/ntfs3: Add missing direct_IO in ntfs_aops_cmpr Lizhi Xu
2025-04-14 5:50 ` 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=67f8679e.050a0220.355867.0018.GAE@google.com \
--to=syzbot+e36cc3297bd3afd25e19@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox