From: syzbot <syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com>
To: amir73il@gmail.com, eric.dumazet@gmail.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
repnop@google.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] KASAN: slab-out-of-bounds Write in __put_unused_fd
Date: Tue, 31 Dec 2024 14:15:01 -0800 [thread overview]
Message-ID: <67746ce5.050a0220.25abdd.0952.GAE@google.com> (raw)
In-Reply-To: <6773f137.050a0220.2f3838.04e2.GAE@google.com>
syzbot has bisected this issue to:
commit ebe559609d7829b52c6642b581860760984faf9d
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Fri Nov 15 15:30:14 2024 +0000
fs: get rid of __FMODE_NONOTIFY kludge
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113e5818580000
start commit: 8155b4ef3466 Add linux-next specific files for 20241220
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=133e5818580000
console output: https://syzkaller.appspot.com/x/log.txt?x=153e5818580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9c90bb7161a56c88
dashboard link: https://syzkaller.appspot.com/bug?extid=6a3aa63412255587b21b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e670b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f42ac4580000
Reported-by: syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com
Fixes: ebe559609d78 ("fs: get rid of __FMODE_NONOTIFY kludge")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-12-31 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 13:27 [syzbot] [fs?] KASAN: slab-out-of-bounds Write in __put_unused_fd syzbot
2024-12-31 13:32 ` Eric Dumazet
2024-12-31 13:41 ` syzbot
2024-12-31 22:15 ` syzbot [this message]
2025-01-01 1:34 ` Hillf Danton
2025-01-01 2:03 ` syzbot
2025-01-06 11:15 ` Jan Kara
2025-01-06 11:49 ` 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=67746ce5.050a0220.25abdd.0952.GAE@google.com \
--to=syzbot+6a3aa63412255587b21b@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=repnop@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox