From: Dmitriy Bogdanov <d.bogdanov@yadro.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux@yadro.com" <linux@yadro.com>
Subject: RE: [PATCH] scsi: target: fix prot handling in WRITE SAME 32
Date: Tue, 29 Jun 2021 16:29:31 +0000 [thread overview]
Message-ID: <f974e27f0393448e814ea0fa1e845d24@yadro.com> (raw)
In-Reply-To: <yq1o8bpl6re.fsf@ca-mkp.ca.oracle.com>
Hi Martin,
> > WRITE SAME 32 command handling reads WRPROTECT at the wrong offset in
> > 1st octet instead of 10th octet.
> Instead of twiddling all these offsets I think it would be cleaner to turn the sbc_setup_write_same() flags[] into an 'unsigned char protect'. And then fix up
> sbc_check_prot() to take 'protect' as argument instead of the full CDB and indexing into that.
OK, I will prepare new version of the patch.
> Another option would be passing the index but since cdb[0] is only used for a rare error message I'm not sure it's worth it.
BR,
Dmitry
prev parent reply other threads:[~2021-06-29 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 9:56 [PATCH] scsi: target: fix prot handling in WRITE SAME 32 Dmitry Bogdanov
2021-06-29 3:01 ` Martin K. Petersen
2021-06-29 16:29 ` Dmitriy Bogdanov [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=f974e27f0393448e814ea0fa1e845d24@yadro.com \
--to=d.bogdanov@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--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).