From: Mike Christie <michael.christie@oracle.com>
To: hch@infradead.org, martin.petersen@oracle.com,
james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: [PATCH 0/1] target: Unmap fixes
Date: Mon, 27 Jun 2022 21:23:24 -0500 [thread overview]
Message-ID: <20220628022325.14627-1-michael.christie@oracle.com> (raw)
This patch made over Linus's tree fixes a crash hit when we get a
WRITE SAME with the NDOB bit set or if the initiator has sent a malformed
WRITE SAME that does not contain any data out buffer even though NDOB=0.
V2:
- This version of patch only fixes the crash. It does not implement
support. Plus other non fix patches put into a feature patchset.
next reply other threads:[~2022-06-28 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 2:23 Mike Christie [this message]
2022-06-28 2:23 ` [PATCH 1/1] scsi: target: Fix WRITE_SAME No Data Buffer crash Mike Christie
2022-06-28 4:54 ` Christoph Hellwig
2022-07-07 20:42 ` Martin K. Petersen
2022-07-07 20:57 ` Dmitry Bogdanov
2022-07-07 21:38 ` Martin K. Petersen
2022-07-07 21:47 ` [PATCH 0/1] target: Unmap fixes Martin K. Petersen
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=20220628022325.14627-1-michael.christie@oracle.com \
--to=michael.christie@oracle.com \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).