From: syzbot <syzbot+8dbe3133b840c470da0e@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] WARNING in sock_map_close (2)
Date: Sat, 24 Aug 2024 05:16:01 -0700 [thread overview]
Message-ID: <000000000000eafa8106206cda75@google.com> (raw)
In-Reply-To: <20240824115705.1267-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in sock_map_link
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6104 at net/core/sock_map.c:206 sock_map_init_proto net/core/sock_map.c:206 [inline]
WARNING: CPU: 0 PID: 6104 at net/core/sock_map.c:206 sock_map_link+0xd6e/0xe40 net/core/sock_map.c:311
Modules linked in:
CPU: 0 UID: 0 PID: 6104 Comm: syz.0.15 Not tainted 6.11.0-rc3-syzkaller-00508-gd785ed945de6-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:sock_map_init_proto net/core/sock_map.c:206 [inline]
RIP: 0010:sock_map_link+0xd6e/0xe40 net/core/sock_map.c:311
Code: ff ff e9 65 f9 ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 34 f3 ff ff 48 89 df e8 4d 90 5a f8 e9 27 f3 ff ff e8 23 4b f3 f7 90 <0f> 0b 90 e9 d9 fd ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c a0 f6
RSP: 0018:ffffc90002d57a60 EFLAGS: 00010293
RAX: ffffffff89a03e4d RBX: ffffffff95312d30 RCX: ffff88802034da00
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff88807dbfda08
RBP: ffffc90002d57b60 R08: ffff88807dbfda0f R09: 1ffff1100fb7fb41
R10: dffffc0000000000 R11: ffffed100fb7fb42 R12: ffff88802b274000
R13: 1ffff920005aaf58 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007f4ea726e6c0(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000440 CR3: 00000000791a4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
sock_hash_update_common+0xd1/0xa30 net/core/sock_map.c:1014
sock_map_update_elem_sys+0x5a4/0x910 net/core/sock_map.c:598
map_update_elem+0x53a/0x6f0 kernel/bpf/syscall.c:1654
__sys_bpf+0x76f/0x810 kernel/bpf/syscall.c:5698
__do_sys_bpf kernel/bpf/syscall.c:5817 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5815 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5815
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4ea6579e79
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4ea726e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f4ea6715f80 RCX: 00007f4ea6579e79
RDX: 0000000000000020 RSI: 0000000020000180 RDI: 0000000000000002
RBP: 00007f4ea65e7916 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f4ea6715f80 R15: 00007ffcfb2f8928
</TASK>
Tested on:
commit: d785ed94 net: wwan: t7xx: PCIe reset rescan
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=148d382b980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7229118d88b4a71b
dashboard link: https://syzkaller.appspot.com/bug?extid=8dbe3133b840c470da0e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11f06d5b980000
next prev parent reply other threads:[~2024-08-24 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 13:19 [syzbot] [bpf?] [net?] WARNING in sock_map_close (2) syzbot
2024-08-23 10:47 ` Hillf Danton
2024-08-23 11:04 ` syzbot
2024-08-24 7:43 ` Hillf Danton
2024-08-24 8:01 ` syzbot
2024-08-24 10:38 ` Hillf Danton
2024-08-24 10:58 ` syzbot
2024-08-24 11:57 ` Hillf Danton
2024-08-24 12:16 ` syzbot [this message]
2024-08-24 23:34 ` Hillf Danton
2024-08-24 23:51 ` 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=000000000000eafa8106206cda75@google.com \
--to=syzbot+8dbe3133b840c470da0e@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.