From: syzbot <syzbot+52bbc0ad036f6f0d4a25@syzkaller.appspotmail.com>
To: 00107082@163.com, coreteam@netfilter.org, davem@davemloft.net,
edumazet@google.com, fw@strlen.de, hdanton@sina.com,
justinstitt@google.com, kadlec@netfilter.org, kuba@kernel.org,
kuniyu@amazon.com, 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: ODEBUG bug in hash_netiface4_destroy
Date: Tue, 06 Feb 2024 22:50:05 -0800 [thread overview]
Message-ID: <000000000000d5018e0610c51a8e@google.com> (raw)
In-Reply-To: <000000000000ecb4750610659876@google.com>
syzbot has bisected this issue to:
commit 97f7cf1cd80eeed3b7c808b7c12463295c751001
Author: Jozsef Kadlecsik <kadlec@netfilter.org>
Date: Mon Jan 29 09:57:01 2024 +0000
netfilter: ipset: fix performance regression in swap operation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=179ff138180000
start commit: 6897cea71837 Merge tag 'for-6.8/dm-fixes' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=145ff138180000
console output: https://syzkaller.appspot.com/x/log.txt?x=105ff138180000
kernel config: https://syzkaller.appspot.com/x/.config?x=457249c250b93697
dashboard link: https://syzkaller.appspot.com/bug?extid=52bbc0ad036f6f0d4a25
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174bd5d3e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16fcf5b0180000
Reported-by: syzbot+52bbc0ad036f6f0d4a25@syzkaller.appspotmail.com
Fixes: 97f7cf1cd80e ("netfilter: ipset: fix performance regression in swap operation")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-02-07 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 12:53 [syzbot] [netfilter?] WARNING: ODEBUG bug in hash_netiface4_destroy syzbot
2024-02-03 3:12 ` syzbot
2024-02-07 6:50 ` 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=000000000000d5018e0610c51a8e@google.com \
--to=syzbot+52bbc0ad036f6f0d4a25@syzkaller.appspotmail.com \
--cc=00107082@163.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=hdanton@sina.com \
--cc=justinstitt@google.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--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 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).