From: syzbot <syzbot+a225fea35d7baf8dbdc3@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, edumazet@google.com,
fw@strlen.de, horms@kernel.org, kadlec@netfilter.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pabeni@redhat.com, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] WARNING in nft_socket_init (2)
Date: Fri, 25 Jul 2025 18:43:03 -0700 [thread overview]
Message-ID: <688432a7.050a0220.1a379b.0001.GAE@google.com> (raw)
In-Reply-To: <68837ca6.a00a0220.2f88df.0053.GAE@google.com>
syzbot has bisected this issue to:
commit 7f3287db654395f9c5ddd246325ff7889f550286
Author: Florian Westphal <fw@strlen.de>
Date: Sat Sep 7 14:07:49 2024 +0000
netfilter: nft_socket: make cgroupsv2 matching work with namespaces
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ff50a2580000
start commit: 94619ea2d933 Merge tag 'ipsec-next-2025-07-23' of git://gi..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1400d0a2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1000d0a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ceda48240b85ec34
dashboard link: https://syzkaller.appspot.com/bug?extid=a225fea35d7baf8dbdc3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12bf10a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d27fd4580000
Reported-by: syzbot+a225fea35d7baf8dbdc3@syzkaller.appspotmail.com
Fixes: 7f3287db6543 ("netfilter: nft_socket: make cgroupsv2 matching work with namespaces")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-07-26 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 12:46 [syzbot] [netfilter?] WARNING in nft_socket_init (2) syzbot
2025-07-25 15:49 ` Pablo Neira Ayuso
2025-07-25 16:22 ` Florian Westphal
2025-07-26 1:43 ` 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=688432a7.050a0220.1a379b.0001.GAE@google.com \
--to=syzbot+a225fea35d7baf8dbdc3@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--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 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.