From: Edward Adam Davis <eadavis@sina.com>
To: eadavis@sina.com
Cc: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: [PATCH v2] fs/ntfs3: Refine the ni cleanup
Date: Thu, 27 Aug 2026 17:43:40 +0800 [thread overview]
Message-ID: <20260827094340.174628-1-eadavis@sina.com> (raw)
In-Reply-To: <20260827081556.168390-1-eadavis@sina.com>
A failure to create a new inode triggered an issue [1] during inode
reclamation because ni->base had not been initialized.
Initialize ni->base earlier to ensure it can be reclaimed correctly.
[1]
KASAN: null-ptr-deref in range [0x0000000000000210-0x0000000000000217]
RIP: 0010:run_close fs/ntfs3/ntfs_fs.h:1034 [inline]
Call Trace:
ni_clear+0x5d/0x630 fs/ntfs3/frecord.c:110
evict+0x624/0xb50 fs/inode.c:822
ntfs_new_inode+0x8c/0x120 fs/ntfs3/fsntfs.c:1719
ntfs_create_inode+0x6e7/0x3420 fs/ntfs3/inode.c:1520
ntfs_mkdir+0x37/0x50 fs/ntfs3/namei.c:234
Fixes: be310476e886 ("fs/ntfs3: Add basic support for alternative data streams")
Reported-by: syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=04cf7b83f6dd2c3a54c8
Tested-by: syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com
Signed-off-by: Edward Adam Davis <eadavis@sina.com>
---
v1 -> v2: unify email addresses
fs/ntfs3/fsntfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/ntfs3/fsntfs.c b/fs/ntfs3/fsntfs.c
index 97c04ab2763a..e439ba59d999 100644
--- a/fs/ntfs3/fsntfs.c
+++ b/fs/ntfs3/fsntfs.c
@@ -1700,6 +1700,7 @@ struct ntfs_inode *ntfs_new_inode(struct ntfs_sb_info *sbi, CLST rno,
return ERR_PTR(-ENOMEM);
ni = ntfs_i(inode);
+ ni->base = ni;
err = mi_format_new(&ni->mi, sbi, rno, flag, false);
if (err)
@@ -1711,8 +1712,6 @@ struct ntfs_inode *ntfs_new_inode(struct ntfs_sb_info *sbi, CLST rno,
goto out;
}
- ni->base = ni;
-
out:
if (err) {
make_bad_inode(inode);
--
2.43.0
prev parent reply other threads:[~2026-08-27 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 20:09 [syzbot] [ntfs3?] general protection fault in al_destroy syzbot
2026-08-27 5:32 ` syzbot
2026-08-27 8:15 ` [PATCH] fs/ntfs3: Refine the ni cleanup Edward Adam Davis
2026-08-27 9:43 ` Edward Adam Davis [this message]
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=20260827094340.174628-1-eadavis@sina.com \
--to=eadavis@sina.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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