public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Greg Edwards <gedwards@ddn.com>
To: virtualization@lists.linux-foundation.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Mike Christie <mchristi@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] vhost/scsi: truncate T10 PI iov_iter to prot_bytes
Date: Fri, 21 Sep 2018 11:49:12 -0600	[thread overview]
Message-ID: <20180921174912.GA19193@psuche> (raw)
In-Reply-To: <20180822192153.24217-1-gedwards@ddn.com>

On Wed, Aug 22, 2018 at 01:21:53PM -0600, Greg Edwards wrote:
> Commands with protection information included were not truncating the
> protection iov_iter to the number of protection bytes in the command.
> This resulted in vhost_scsi mis-calculating the size of the protection
> SGL in vhost_scsi_calc_sgls(), and including both the protection and
> data SG entries in the protection SGL.
>
> Fixes: 09b13fa8c1a1 ("vhost/scsi: Add ANY_LAYOUT support in vhost_scsi_handle_vq")
> Signed-off-by: Greg Edwards <gedwards@ddn.com>


Any thoughts on this patch?


> ---
>  drivers/vhost/scsi.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c
> index 76f8d649147b..cbe0ea26c1ff 100644
> --- a/drivers/vhost/scsi.c
> +++ b/drivers/vhost/scsi.c
> @@ -964,7 +964,8 @@ vhost_scsi_handle_vq(struct vhost_scsi *vs, struct vhost_virtqueue *vq)
>  				prot_bytes = vhost32_to_cpu(vq, v_req_pi.pi_bytesin);
>  			}
>  			/*
> -			 * Set prot_iter to data_iter, and advance past any
> +			 * Set prot_iter to data_iter and truncate it to
> +			 * prot_bytes, and advance data_iter past any
>  			 * preceeding prot_bytes that may be present.
>  			 *
>  			 * Also fix up the exp_data_len to reflect only the
> @@ -973,6 +974,7 @@ vhost_scsi_handle_vq(struct vhost_scsi *vs, struct vhost_virtqueue *vq)
>  			if (prot_bytes) {
>  				exp_data_len -= prot_bytes;
>  				prot_iter = data_iter;
> +				iov_iter_truncate(&prot_iter, prot_bytes);
>  				iov_iter_advance(&data_iter, prot_bytes);
>  			}
>  			tag = vhost64_to_cpu(vq, v_req_pi.tag);
> --
> 2.17.1

  reply	other threads:[~2018-09-21 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 19:21 [PATCH] vhost/scsi: truncate T10 PI iov_iter to prot_bytes Greg Edwards
2018-09-21 17:49 ` Greg Edwards [this message]
2018-09-21 17:57   ` Michael S. Tsirkin
2018-09-24  9:09   ` Paolo Bonzini

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=20180921174912.GA19193@psuche \
    --to=gedwards@ddn.com \
    --cc=mchristi@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=virtualization@lists.linux-foundation.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