From: syzbot <syzbot+d8f76778263ab65c2b21@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yanjun.zhu@linux.dev, zyjzyj2000@gmail.com
Subject: Re: [syzbot] [rdma] general protection fault in kernel_sock_shutdown (4)
Date: Fri, 29 May 2026 19:08:03 -0700 [thread overview]
Message-ID: <6a1a4683.b111c304.35cd64.0015.GAE@google.com> (raw)
In-Reply-To: <4c71307f-b868-4f31-a1bc-30c039e3f930@linux.dev>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: f569da7e DMA/rxe: Use rtnl_lock/unlock to fix it
git tree: https://github.com/zhuyj/linux null-ptr-deref_kernel_sock_shutdown
console output: https://syzkaller.appspot.com/x/log.txt?x=104669a6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8dc2c248e04d231d
dashboard link: https://syzkaller.appspot.com/bug?extid=d8f76778263ab65c2b21
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Note: no patches were applied.
next parent reply other threads:[~2026-05-30 2:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4c71307f-b868-4f31-a1bc-30c039e3f930@linux.dev>
2026-05-30 2:08 ` syzbot [this message]
2026-05-30 2:14 ` Zhu Yanjun
[not found] <7b5a4b26-996c-497a-9db7-e387063e9f53@linux.dev>
2026-05-29 23:45 ` syzbot
[not found] <ae525a97-4837-41b4-9883-8ac008d911a4@linux.dev>
2026-05-16 21:01 ` syzbot
2026-05-16 21:35 ` Zhu Yanjun
2026-05-16 22:11 ` syzbot
2026-04-23 15:01 [syzbot] [net?] " syzbot
2026-05-06 13:48 ` [syzbot] [rdma] " syzbot
2026-05-06 14:28 ` Zhu Yanjun
2026-05-06 15:19 ` Kuniyuki Iwashima
2026-05-07 1:30 ` Hillf Danton
2026-05-07 1:57 ` syzbot
2026-05-07 3:52 ` syzbot
2026-05-07 10:12 ` Edward Adam Davis
2026-05-07 12:02 ` syzbot
2026-05-14 5:15 ` Zhu Yanjun
2026-05-16 5:44 ` Zhu Yanjun
2026-05-16 7:02 ` syzbot
2026-05-16 18:40 ` Zhu Yanjun
2026-05-16 12:40 ` Edward Adam Davis
2026-05-16 13:26 ` 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=6a1a4683.b111c304.35cd64.0015.GAE@google.com \
--to=syzbot+d8f76778263ab65c2b21@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yanjun.zhu@linux.dev \
--cc=zyjzyj2000@gmail.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
Powered by JetHome