From: Edward Adam Davis <eadavis@sina.com>
To: syzbot+04cf7b83f6dd2c3a54c8@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Read in stub_rx_loop
Date: Thu, 27 Aug 2026 15:03:05 +0800 [thread overview]
Message-ID: <20260827070305.162124-1-eadavis@sina.com> (raw)
In-Reply-To: <6a8fcbe6.4d659fcc.734b4.000a.GAE@google.com>
From: Edward Aadm Davis <eadavis@sina.com>
#syz test: upstream 502d45774af0
diff --git a/fs/ntfs3/fsntfs.c b/fs/ntfs3/fsntfs.c
index 97c04ab2763a..cea5d86a5591 100644
--- a/fs/ntfs3/fsntfs.c
+++ b/fs/ntfs3/fsntfs.c
@@ -1701,6 +1701,7 @@ struct ntfs_inode *ntfs_new_inode(struct ntfs_sb_info *sbi, CLST rno,
ni = ntfs_i(inode);
+ ni->base = ni;
err = mi_format_new(&ni->mi, sbi, rno, flag, false);
if (err)
goto out;
@@ -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);
next prev parent reply other threads:[~2026-08-27 7:03 UTC|newest]
Thread overview: 22+ 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 7:03 ` Edward Adam Davis [this message]
2026-08-27 8:11 ` syzbot
2026-08-27 8:15 ` [PATCH] fs/ntfs3: Refine the ni cleanup Edward Adam Davis
2026-08-27 9:43 ` [PATCH v2] " Edward Adam Davis
-- strict thread matches above, loose matches on Subject: below --
2026-07-28 14:25 [syzbot] [usb?] KASAN: slab-use-after-free Read in stub_rx_loop syzbot
2026-08-26 16:49 ` syzbot
2026-08-26 23:32 ` Hillf Danton
2026-08-26 23:33 ` syzbot
2026-08-26 23:46 ` Hillf Danton
2026-08-26 23:46 ` syzbot
2026-08-27 0:06 ` Hillf Danton
2026-08-27 0:06 ` syzbot
2026-08-27 0:17 ` Hillf Danton
2026-08-27 0:18 ` syzbot
2026-08-27 0:20 ` Hillf Danton
2026-08-27 0:21 ` syzbot
2026-08-27 0:25 ` Hillf Danton
2026-08-27 2:12 ` syzbot
2026-08-27 0:46 ` Edward Adam Davis
2026-08-27 2:31 ` syzbot
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=20260827070305.162124-1-eadavis@sina.com \
--to=eadavis@sina.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®