From: syzbot <syzbot+78ac1e46d2966eb70fda@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, phil@nwl.cc,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (9)
Date: Thu, 30 Oct 2025 18:51:02 -0700 [thread overview]
Message-ID: <69041606.050a0220.32483.0233.GAE@google.com> (raw)
In-Reply-To: <aQQLJtqY44w1iD2b@orbyte.nwl.cc>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+78ac1e46d2966eb70fda@syzkaller.appspotmail.com
Tested-by: syzbot+78ac1e46d2966eb70fda@syzkaller.appspotmail.com
Tested on:
commit: 12a7c6a9 Merge tag 'nf-next-25-10-30' of https://git.k..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12f74e14580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5683686a5f7ee53f
dashboard link: https://syzkaller.appspot.com/bug?extid=78ac1e46d2966eb70fda
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11b3cbcd980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-31 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aQQLJtqY44w1iD2b@orbyte.nwl.cc>
2025-10-31 1:51 ` syzbot [this message]
[not found] <aaGSG1ermkScHc-3@orbyte.nwl.cc>
2026-02-27 13:18 ` [syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (9) syzbot
[not found] <aaFxCF4ia6k1Umo1@orbyte.nwl.cc>
2026-02-27 11:52 ` syzbot
[not found] <aaB3QhwYC6psSM-p@orbyte.nwl.cc>
2026-02-26 18:55 ` syzbot
[not found] <aWpDy3rhKZLmx4Ii@orbyte.nwl.cc>
2026-01-16 15:06 ` syzbot
[not found] <aQTg3jUfRB9cCBv2@orbyte.nwl.cc>
2025-10-31 18:54 ` syzbot
[not found] <aQSN9-E4Q7fdlQ2C@orbyte.nwl.cc>
2025-10-31 11:31 ` syzbot
2025-07-30 5:30 syzbot
2025-10-30 12:37 ` syzbot
2025-10-31 16:15 ` Phil Sutter
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=69041606.050a0220.32483.0233.GAE@google.com \
--to=syzbot+78ac1e46d2966eb70fda@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@nwl.cc \
--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.