From: syzbot <syzbot+dcc068159182a4c31ca3@syzkaller.appspotmail.com>
To: brauner@kernel.org, dmantipov@yandex.ru, jack@suse.cz,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, mjguzik@gmail.com,
shaggy@kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode
Date: Wed, 07 Jan 2026 06:57:02 -0800 [thread overview]
Message-ID: <695e743e.050a0220.1c677c.036a.GAE@google.com> (raw)
In-Reply-To: <00000000000051d14405fadad8cc@google.com>
syzbot suspects this issue was fixed by commit:
commit dca3aa666fbd71118905d88bb1c353881002b647
Author: Mateusz Guzik <mjguzik@gmail.com>
Date: Sun Nov 9 12:19:31 2025 +0000
fs: move inode fields used during fast path lookup closer together
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1480019a580000
start commit: 6146a0f1dfae Linux 6.18-rc4
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e46b8a1c645465a9
dashboard link: https://syzkaller.appspot.com/bug?extid=dcc068159182a4c31ca3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15ef4532580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=179c1e14580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: move inode fields used during fast path lookup closer together
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2026-01-07 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 9:32 [syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode syzbot
2025-09-24 19:11 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cec1e6e5d1ab33403b809f79cd20d6aff124ccfe syzbot
2026-01-07 14:57 ` syzbot [this message]
2026-01-07 15:05 ` [syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode Mateusz Guzik
[not found] <ca3d9dd2-f97c-4bad-a60e-4aef39e9cab1@yandex.ru>
2025-09-24 19:42 ` 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=695e743e.050a0220.1c677c.036a.GAE@google.com \
--to=syzbot+dcc068159182a4c31ca3@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mjguzik@gmail.com \
--cc=shaggy@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox