qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, benoit.canet@irqsave.net,
	ronniesahlberg@gmail.com, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block/iscsi: always fill bs->bl.opt_transfer_length
Date: Wed, 29 Jan 2014 16:36:07 +0100	[thread overview]
Message-ID: <20140129153606.GD3079@irqsave.net> (raw)
In-Reply-To: <1390997015-19609-1-git-send-email-pl@kamp.de>

Le Wednesday 29 Jan 2014 à 13:03:35 (+0100), Peter Lieven a écrit :
> the opt_transfer_length has nothing to do with logical
> block provisioning stuff so always copy it from
> the block limits VPD page.
> 
> Reported-By: Benoit Canet <benoit@irqsave.net>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
>  block/iscsi.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/block/iscsi.c b/block/iscsi.c
> index 38b07f8..3c0b728 100644
> --- a/block/iscsi.c
> +++ b/block/iscsi.c
> @@ -1331,10 +1331,9 @@ static int iscsi_refresh_limits(BlockDriverState *bs)
>          }
>          bs->bl.write_zeroes_alignment = sector_lun2qemu(iscsilun->bl.opt_unmap_gran,
>                                                          iscsilun);
> -
> -        bs->bl.opt_transfer_length = sector_lun2qemu(iscsilun->bl.opt_xfer_len,
> -                                                     iscsilun);
>      }
> +    bs->bl.opt_transfer_length = sector_lun2qemu(iscsilun->bl.opt_xfer_len,
> +                                                 iscsilun);
>      return 0;
>  }
>  
> -- 
> 1.7.9.5
> 
Reviewed-by: Benoit Canet <benoit@irqsave.net>

       reply	other threads:[~2014-01-29 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1390997015-19609-1-git-send-email-pl@kamp.de>
2014-01-29 15:36 ` Benoît Canet [this message]
2014-02-03 15:57   ` [Qemu-devel] [PATCH] block/iscsi: always fill bs->bl.opt_transfer_length Kevin Wolf

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=20140129153606.GD3079@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=kwolf@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=stefanha@redhat.com \
    /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).