From: syzbot <syzbot+169de184e9defe7fe709@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nfs?] [net?] possible deadlock in rpc_close_pipes
Date: Thu, 03 Jul 2025 02:11:03 -0700 [thread overview]
Message-ID: <68664927.a70a0220.5d25f.0862.GAE@google.com> (raw)
In-Reply-To: <20250703024751.1194841-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+169de184e9defe7fe709@syzkaller.appspotmail.com
Tested-by: syzbot+169de184e9defe7fe709@syzkaller.appspotmail.com
Tested on:
commit: 50c8770a Add linux-next specific files for 20250702
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16dff982580000
kernel config: https://syzkaller.appspot.com/x/.config?x=76d012e863976d4c
dashboard link: https://syzkaller.appspot.com/bug?extid=169de184e9defe7fe709
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=1336f982580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-07-03 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250703024751.1194841-1-lizhi.xu@windriver.com>
2025-07-03 9:11 ` syzbot [this message]
[not found] <20250703092239.1891519-1-lizhi.xu@windriver.com>
2025-07-03 11:20 ` [syzbot] [nfs?] [net?] possible deadlock in rpc_close_pipes syzbot
[not found] <20250703011717.3952009-1-lizhi.xu@windriver.com>
2025-07-03 8:35 ` syzbot
2025-07-03 2:59 [syzbot] " Al Viro
2025-07-03 9:38 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-07-02 17:41 syzbot
2025-07-03 1:40 ` Hillf Danton
2025-07-03 8:58 ` 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=68664927.a70a0220.5d25f.0862.GAE@google.com \
--to=syzbot+169de184e9defe7fe709@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox