From: syzbot <syzbot+9f4a135646b66c509935@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yun.zhou@windriver.com
Subject: Re: [syzbot] [net?] possible deadlock in __sk_receive_skb
Date: Tue, 19 May 2026 19:33:02 -0700 [thread overview]
Message-ID: <6a0d1d5e.a70a0220.1a69d3.001b.GAE@google.com> (raw)
In-Reply-To: <558b914a-3c66-4c23-8f04-1f75cb145b61@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: 6a50ba10 Add linux-next specific files for 20260519
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1132ecec580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c291f7fbe0370431
dashboard link: https://syzkaller.appspot.com/bug?extid=9f4a135646b66c509935
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=107d002e580000
next parent reply other threads:[~2026-05-20 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <558b914a-3c66-4c23-8f04-1f75cb145b61@windriver.com>
2026-05-20 2:33 ` syzbot [this message]
[not found] <CH0PR11MB5332ACD8185B2A3BDDF372419F012@CH0PR11MB5332.namprd11.prod.outlook.com>
2026-05-20 14:59 ` [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
[not found] <CH0PR11MB5332860984149DC56D1BBE449F012@CH0PR11MB5332.namprd11.prod.outlook.com>
2026-05-20 12:06 ` syzbot
[not found] <CH0PR11MB53320EABCC62F152BEFF7FA79F012@CH0PR11MB5332.namprd11.prod.outlook.com>
2026-05-20 11:19 ` syzbot
[not found] <CH0PR11MB53327F133B468B6D445872749F012@CH0PR11MB5332.namprd11.prod.outlook.com>
2026-05-20 9:48 ` syzbot
2026-05-19 18:53 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=6a0d1d5e.a70a0220.1a69d3.001b.GAE@google.com \
--to=syzbot+9f4a135646b66c509935@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yun.zhou@windriver.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