From: Dmitry Bogdanov <d.bogdanov@yadro.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Mike Christie <michael.christie@oracle.com>,
<james.bottomley@hansenpartnership.com>,
<linux-scsi@vger.kernel.org>, <target-devel@vger.kernel.org>
Subject: Re: [PATCH 1/1] scsi: target: Fix WRITE_SAME No Data Buffer crash
Date: Thu, 7 Jul 2022 23:57:51 +0300 [thread overview]
Message-ID: <20220707205751.GA3509@yadro.com> (raw)
In-Reply-To: <yq1mtdk7j59.fsf@ca-mkp.ca.oracle.com>
Hi Martin,
On Thu, Jul 07, 2022 at 04:42:36PM -0400, Martin K. Petersen wrote:
>
> Christoph,
>
> > (and I wonder if we have similar problems with other commands, the
> > target code could use same targeted fuzzing..)
>
> Yeah.
>
> The USB gadget series implements initial support for RSOC. It might be
> worth entertaining to augment that code with CDB masks for all the
> commands we actually support. And then leverage these masks for command
> validation.
I have a patchset with complete RSOC support with CDB mask. Even dynamic
mask due to device configuration. It passes all RSOC related libiscsi
tests.
If the community want it I may send it.
next prev parent reply other threads:[~2022-07-07 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 2:23 [PATCH 0/1] target: Unmap fixes Mike Christie
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 [this message]
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=20220707205751.GA3509@yadro.com \
--to=d.bogdanov@yadro.com \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.