From: syzbot <syzbot+f3f3eef1d2100200e593@syzkaller.appspotmail.com>
To: axboe@kernel.dk, davem@davemloft.net, edumazet@google.com,
hdanton@sina.com, kuba@kernel.org, kuni1840@gmail.com,
kuniyu@amazon.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in unix_del_edges
Date: Sat, 20 Apr 2024 21:06:04 -0700 [thread overview]
Message-ID: <00000000000089f36106169370d0@google.com> (raw)
In-Reply-To: <000000000000c1fa0506166fdcfe@google.com>
syzbot has bisected this issue to:
commit 77e5593aebba823bcbcf2c4b58b07efcd63933b8
Author: Kuniyuki Iwashima <kuniyu@amazon.com>
Date: Mon Mar 25 20:24:20 2024 +0000
af_unix: Skip GC if no cycle exists.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14bbda4f180000
start commit: 7b4f2bc91c15 Add linux-next specific files for 20240418
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16bbda4f180000
console output: https://syzkaller.appspot.com/x/log.txt?x=12bbda4f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=ae644165a243bf62
dashboard link: https://syzkaller.appspot.com/bug?extid=f3f3eef1d2100200e593
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155e53af180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128b1d53180000
Reported-by: syzbot+f3f3eef1d2100200e593@syzkaller.appspotmail.com
Fixes: 77e5593aebba ("af_unix: Skip GC if no cycle exists.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-04-21 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:39 [syzbot] [net?] KASAN: slab-use-after-free Read in unix_del_edges syzbot
2024-04-19 19:17 ` Kuniyuki Iwashima
2024-04-19 20:39 ` Kuniyuki Iwashima
2024-04-19 21:13 ` syzbot
2024-04-21 4:06 ` syzbot [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=00000000000089f36106169370d0@google.com \
--to=syzbot+f3f3eef1d2100200e593@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).