From: syzbot <syzbot+de4025c006ec68ac56fc@syzkaller.appspotmail.com>
To: fw@strlen.de, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (6)
Date: Mon, 19 Feb 2024 07:05:04 -0800 [thread overview]
Message-ID: <0000000000002f3c3a0611bd6b5e@google.com> (raw)
In-Reply-To: <20240219140408.GB22070@breakpoint.cc>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+de4025c006ec68ac56fc@syzkaller.appspotmail.com
Tested on:
commit: 34bfd872 netfilter: nf_tables: raise dormant flag agai..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/fwestphal/nf.git dormant-reset
console output: https://syzkaller.appspot.com/x/log.txt?x=1495c734180000
kernel config: https://syzkaller.appspot.com/x/.config?x=52f6b87f61a6b59c
dashboard link: https://syzkaller.appspot.com/bug?extid=de4025c006ec68ac56fc
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-02-19 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240219140408.GB22070@breakpoint.cc>
2024-02-19 15:05 ` syzbot [this message]
[not found] <20240217123828.GA31625@breakpoint.cc>
2024-02-17 12:55 ` [syzbot] [netfilter?] WARNING in __nf_unregister_net_hook (6) syzbot
[not found] <20231120105551.1784323-1-eadavis@sina.com>
2023-11-20 11:34 ` syzbot
[not found] <20231120030705.1265508-1-eadavis@sina.com>
2023-11-20 3:43 ` syzbot
[not found] <20231119103215.698030-1-eadavis@sina.com>
2023-11-19 11:11 ` syzbot
[not found] <20231119051509.330056-1-eadavis@sina.com>
2023-11-19 6:12 ` syzbot
[not found] <20231105050015.2524557-1-eadavis@sina.com>
2023-11-05 5:16 ` syzbot
2023-10-17 18:04 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=0000000000002f3c3a0611bd6b5e@google.com \
--to=syzbot+de4025c006ec68ac56fc@syzkaller.appspotmail.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.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