From: syzbot <syzbot+2459c1b9fcd39be822b1@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, davem@davemloft.net,
dsahern@kernel.org, eddyz87@gmail.com, edumazet@google.com,
hdanton@sina.com, jolsa@kernel.org, kuba@kernel.org,
laoar.shao@gmail.com, linux-kernel@vger.kernel.org,
martin.lau@kernel.org, netdev@vger.kernel.org,
olsajiri@gmail.com, pabeni@redhat.com, sdf@google.com,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [net?] WARNING in inet_csk_get_port (3)
Date: Tue, 23 Jul 2024 09:38:03 -0700 [thread overview]
Message-ID: <000000000000124c1f061decc9d5@google.com> (raw)
In-Reply-To: <0000000000005736990617c4fa63@google.com>
syzbot suspects this issue was fixed by commit:
commit 543576ec15b17c0c93301ac8297333c7b6e84ac7
Author: Stanislav Fomichev <sdf@google.com>
Date: Fri Apr 26 23:16:18 2024 +0000
bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f0b0c9980000
start commit: 977b1ef51866 Merge tag 'block-6.9-20240420' of git://git.k..
git tree: upstream
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
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-07-23 16:38 UTC|newest]
Thread overview: 4+ 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
2024-05-27 8:12 ` Jiri Olsa
2024-07-23 16:38 ` 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=000000000000124c1f061decc9d5@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=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=pabeni@redhat.com \
--cc=sdf@google.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 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).