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: Sat, 17 Feb 2024 04:55:02 -0800 [thread overview]
Message-ID: <000000000000723bee0611935ee4@google.com> (raw)
In-Reply-To: <20240217123828.GA31625@breakpoint.cc>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __nf_unregister_net_hook
------------[ cut here ]------------
hook not found, pf 2 num 1
WARNING: CPU: 1 PID: 5828 at net/netfilter/core.c:517 __nf_unregister_net_hook+0x1de/0x670 net/netfilter/core.c:517
Modules linked in:
CPU: 1 PID: 5828 Comm: syz-executor.3 Not tainted 6.8.0-rc3-syzkaller-00211-g84443741faab #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:__nf_unregister_net_hook+0x1de/0x670 net/netfilter/core.c:517
Code: 14 02 4c 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 7a 04 00 00 8b 53 1c 48 c7 c7 a0 ab ab 8b 8b 74 24 04 e8 b2 64 c6 f8 <0f> 0b e9 ec 00 00 00 e8 f6 f9 00 f9 48 89 e8 48 c1 e0 04 49 8d 7c
RSP: 0018:ffffc90003c272b0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff88807dd4da00 RCX: ffffffff814d93f9
RDX: ffff88802c4c9dc0 RSI: ffffffff814d9406 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff8880699cad90
R13: ffff8880648246f8 R14: ffff888064824660 R15: ffff88807dd4da1c
FS: 00007f51415d46c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f51415b3d58 CR3: 000000007fa81000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nf_unregister_net_hook+0xd5/0x110 net/netfilter/core.c:539
__nf_tables_unregister_hook net/netfilter/nf_tables_api.c:362 [inline]
__nf_tables_unregister_hook+0x1a0/0x220 net/netfilter/nf_tables_api.c:341
nf_tables_unregister_hook net/netfilter/nf_tables_api.c:369 [inline]
nf_tables_commit+0x3cdb/0x5ae0 net/netfilter/nf_tables_api.c:10174
nfnetlink_rcv_batch+0xf3b/0x2510 net/netfilter/nfnetlink.c:569
nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:639 [inline]
nfnetlink_rcv+0x3bf/0x430 net/netfilter/nfnetlink.c:657
netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]
netlink_unicast+0x53b/0x810 net/netlink/af_netlink.c:1367
netlink_sendmsg+0x8b7/0xd70 net/netlink/af_netlink.c:1908
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg+0xd5/0x180 net/socket.c:745
____sys_sendmsg+0x6ac/0x940 net/socket.c:2584
___sys_sendmsg+0x135/0x1d0 net/socket.c:2638
__sys_sendmsg+0x117/0x1e0 net/socket.c:2667
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x78/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f514087cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f51415d40c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f514099c050 RCX: 00007f514087cae9
RDX: 0000000000000000 RSI: 000000002000c2c0 RDI: 0000000000000004
RBP: 00007f51408c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f514099c050 R15: 00007ffd31c3ba48
</TASK>
Tested on:
commit: 84443741 netfilter: nf_tables: fix bidirectional offlo..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=11a08ae8180000
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.
next parent reply other threads:[~2024-02-17 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240217123828.GA31625@breakpoint.cc>
2024-02-17 12:55 ` syzbot [this message]
[not found] <20240219140408.GB22070@breakpoint.cc>
2024-02-19 15:05 ` [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=000000000000723bee0611935ee4@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 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.