All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2459c1b9fcd39be822b1@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in inet_csk_get_port (3)
Date: Mon, 27 May 2024 14:06:06 -0700	[thread overview]
Message-ID: <000000000000bb3fe9061975e254@google.com> (raw)
In-Reply-To: <20240527104512.2559-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-.... } 2676 jiffies s: 3265 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 6099 Comm: syz-executor.1 Not tainted 6.9.0-rc4-syzkaller-00266-g977b1ef51866-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:write_comp_data+0x34/0x90 kernel/kcov.c:236
Code: 48 8b 15 ff 1b 76 7e 65 8b 05 00 1c 76 7e a9 00 01 ff 00 74 0f f6 c4 01 74 59 8b 82 14 16 00 00 85 c0 74 4f 8b 82 f0 15 00 00 <83> f8 03 75 44 48 8b 82 f8 15 00 00 8b 92 f4 15 00 00 48 8b 38 48
RSP: 0018:ffffc90002e5fc88 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff888068e7cb40 RCX: ffffffff894209a1
RDX: ffff88801bfa8000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffff888068e7cb40 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000020 R11: 0000000000000003 R12: dffffc0000000000
R13: 0000000000000020 R14: 0000000000000000 R15: ffffed100d1cf96a
FS:  00007fe3784b36c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7b05dac000 CR3: 0000000011a78000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 __inet_bhash2_conflict net/ipv4/inet_connection_sock.c:206 [inline]
 inet_bhash2_conflict.isra.0+0xb1/0x210 net/ipv4/inet_connection_sock.c:229
 inet_csk_bind_conflict+0x40c/0x630 net/ipv4/inet_connection_sock.c:264
 inet_csk_get_port+0x1639/0x25b0 net/ipv4/inet_connection_sock.c:585
 inet_csk_listen_start+0x15e/0x390 net/ipv4/inet_connection_sock.c:1281
 inet_dccp_listen+0x1c5/0x220 net/dccp/proto.c:951
 __sys_listen+0x19b/0x280 net/socket.c:1881
 __do_sys_listen net/socket.c:1890 [inline]
 __se_sys_listen net/socket.c:1888 [inline]
 __x64_sys_listen+0x53/0x80 net/socket.c:1888
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe37767dea9
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:00007fe3784b30c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000032
RAX: ffffffffffffffda RBX: 00007fe3777abf80 RCX: 00007fe37767dea9
RDX: 0000000000000000 RSI: 0000000020000005 RDI: 0000000000000003
RBP: 00007fe3776ca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fe3777abf80 R15: 00007fff4057e238
 </TASK>


Tested on:

commit:         977b1ef5 Merge tag 'block-6.9-20240420' of git://git.k..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1530f71a980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=85dbe39cf8e4f599
dashboard link: https://syzkaller.appspot.com/bug?extid=2459c1b9fcd39be822b1
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=13e5e7f0980000


  reply	other threads:[~2024-05-27 21:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  8:37 [syzbot] [net?] WARNING in inet_csk_get_port (3) syzbot
2024-05-26 12:20 ` syzbot
2024-05-27  8:12   ` Jiri Olsa
2024-05-26 23:27 ` Hillf Danton
2024-05-27  0:19   ` syzbot
2024-05-27 10:45 ` Hillf Danton
2024-05-27 21:06   ` syzbot [this message]
2024-07-23 16:38 ` 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=000000000000bb3fe9061975e254@google.com \
    --to=syzbot+2459c1b9fcd39be822b1@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --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.