From: syzbot <syzbot+f9db6ff27b9bfdcfeca0@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: [syzbot] [rds?] possible deadlock in rds_message_put
Date: Tue, 30 Jan 2024 20:11:03 -0800 [thread overview]
Message-ID: <00000000000035876106103611b8@google.com> (raw)
In-Reply-To: <0000000000005315c105f1652480@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [rds?] possible deadlock in rds_message_put
Author: allison.henderson@oracle.com
#syz test: https://github.com/allisonhenderson/rds_work syzbug_f9db6ff27b9bfdcfeca
prev parent reply other threads:[~2024-01-31 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 0:19 [syzbot] possible deadlock in rds_message_put syzbot
2023-01-04 3:39 ` Jason Wang
2024-01-30 19:58 ` [syzbot] Test " syzbot
2024-01-31 4:11 ` syzbot [this message]
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=00000000000035876106103611b8@google.com \
--to=syzbot+f9db6ff27b9bfdcfeca0@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox