From: syzbot <syzbot+2459c1b9fcd39be822b1@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, jolsa@kernel.org,
kuba@kernel.org, laoar.shao@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
yonghong.song@linux.dev
Subject: Re: [syzbot] [net?] WARNING in inet_csk_get_port (3)
Date: Sun, 26 May 2024 05:20:06 -0700 [thread overview]
Message-ID: <000000000000c53d3206195a6b38@google.com> (raw)
In-Reply-To: <0000000000005736990617c4fa63@google.com>
syzbot has bisected this issue to:
commit 3505cb9fa26cfec9512744466e754a8cbc2365b0
Author: Jiri Olsa <jolsa@kernel.org>
Date: Wed Aug 9 08:34:14 2023 +0000
bpf: Add attach_type checks under bpf_prog_attach_check_attach_type
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15dbe672980000
start commit: 977b1ef51866 Merge tag 'block-6.9-20240420' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17dbe672980000
console output: https://syzkaller.appspot.com/x/log.txt?x=13dbe672980000
kernel config: https://syzkaller.appspot.com/x/.config?x=85dbe39cf8e4f599
dashboard link: https://syzkaller.appspot.com/bug?extid=2459c1b9fcd39be822b1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126c6080980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11135520980000
Reported-by: syzbot+2459c1b9fcd39be822b1@syzkaller.appspotmail.com
Fixes: 3505cb9fa26c ("bpf: Add attach_type checks under bpf_prog_attach_check_attach_type")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-05-26 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 8:37 [syzbot] [net?] WARNING in inet_csk_get_port (3) syzbot
2024-05-26 12:20 ` syzbot [this message]
2024-05-27 8:12 ` Jiri Olsa
2024-05-26 23:27 ` Hillf Danton
2024-05-27 0:19 ` syzbot
2024-05-27 10:45 ` Hillf Danton
2024-05-27 21:06 ` syzbot
2024-07-23 16:38 ` 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=000000000000c53d3206195a6b38@google.com \
--to=syzbot+2459c1b9fcd39be822b1@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.