From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 212759] NvmeOf (nvmet-rdma) cause crash with first step connect
Date: Tue, 27 Apr 2021 09:01:00 +0000 [thread overview]
Message-ID: <bug-212759-11613-kTC7DZfS2U@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212759-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212759
Badalian Slava (slavon.net@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Other |NVMe
Kernel Version|5.11.14 - 5.11.16 |5.11.16
Product|SCSI Drivers |IO/Storage
Summary|NVMeT crasdh |NvmeOf (nvmet-rdma) cause
| |crash with first step
| |connect
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-04-27 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 4:41 [Bug 212759] New: NVMeT crasdh bugzilla-daemon
2021-04-23 4:42 ` [Bug 212759] " bugzilla-daemon
2021-04-27 8:59 ` bugzilla-daemon
2021-04-27 9:01 ` bugzilla-daemon [this message]
2021-04-27 9:05 ` [Bug 212759] NvmeOf (nvmet-rdma) cause crash with first step connect bugzilla-daemon
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=bug-212759-11613-kTC7DZfS2U@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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