Hello,
syzbot found the following issue on:
HEAD commit: 610bdbf6 Linux 4.19.166
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12943b0b500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=18ac8e7164be61b2
dashboard link:
https://syzkaller.appspot.com/bug?extid=3bd41ec8bcffeccedda9
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3bd41e...@syzkaller.appspotmail.com
x_tables: ip_tables: rpfilter match: used from hooks INPUT, but only valid from PREROUTING
------------[ cut here ]------------
proc_dir_entry 'ipt_CLUSTERIP/
172.20.20.187' already registered
WARNING: CPU: 0 PID: 22300 at fs/proc/generic.c:359 proc_register+0x34c/0x6c0 fs/proc/generic.c:359
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 22300 Comm: syz-executor.5 Not tainted 4.19.166-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:proc_register+0x34c/0x6c0 fs/proc/generic.c:359
Code: df 48 89 f9 48 c1 e9 03 80 3c 01 00 0f 85 24 03 00 00 48 8b 44 24 28 48 c7 c7 60 e9 76 88 48 8b b0 d0 00 00 00 e8 7f b0 73 ff <0f> 0b 48 c7 c7 c0 99 06 8a e8 16 04 51 06 48 8b 4c 24 38 48 b8 00
RSP: 0018:ffff8881f9377660 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814fdd11 RDI: ffffed103f26eebe
RBP: ffff8880a9bd50f0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880a14a7b90
R13: ffff888097629e78 R14: dffffc0000000000 R15: 000000000000000d
proc_create_data+0xc4/0x120 fs/proc/generic.c:548
clusterip_config_init net/ipv4/netfilter/ipt_CLUSTERIP.c:285 [inline]
clusterip_tg_check+0x10fe/0x15e0 net/ipv4/netfilter/ipt_CLUSTERIP.c:506
xt_check_target+0x26c/0x650 net/netfilter/x_tables.c:1024
check_target net/ipv4/netfilter/ip_tables.c:514 [inline]
find_check_entry.constprop.0+0x7a9/0x9a0 net/ipv4/netfilter/ip_tables.c:556
translate_table+0xbe1/0x1600 net/ipv4/netfilter/ip_tables.c:720
do_replace net/ipv4/netfilter/ip_tables.c:1139 [inline]
do_ipt_set_ctl+0x29d/0x420 net/ipv4/netfilter/ip_tables.c:1675
nf_sockopt net/netfilter/nf_sockopt.c:106 [inline]
nf_setsockopt+0x6f/0xc0 net/netfilter/nf_sockopt.c:115
ip_setsockopt net/ipv4/ip_sockglue.c:1258 [inline]
ip_setsockopt+0xd8/0xf0 net/ipv4/ip_sockglue.c:1238
udp_setsockopt+0x5d/0xa0 net/ipv4/udp.c:2552
__sys_setsockopt+0x14d/0x240 net/socket.c:1901
__do_sys_setsockopt net/socket.c:1912 [inline]
__se_sys_setsockopt net/socket.c:1909 [inline]
__x64_sys_setsockopt+0xba/0x150 net/socket.c:1909
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45e219
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f567e4ffc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 000000000045e219
RDX: 0000000000000040 RSI: 0004000000000000 RDI: 0000000000000006
RBP: 000000000119bfd0 R08: 00000000000002c8 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007ffe2512e64f R14: 00007f567e5009c0 R15: 000000000119bf8c
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.