From: Max Reitz <mreitz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, benoit@irqsave.net,
ronniesahlberg@gmail.com, armbru@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv5 5/6] block/iscsi: limit to INT_MAX throughout iscsi_refresh_limits
Date: Mon, 27 Oct 2014 09:38:43 +0100 [thread overview]
Message-ID: <544E0493.7060403@redhat.com> (raw)
In-Reply-To: <544E03EB.7090207@kamp.de>
On 2014-10-27 at 09:35, Peter Lieven wrote:
> On 27.10.2014 09:32, Max Reitz wrote:
>> On 2014-10-25 at 18:18, Peter Lieven wrote:
>>> As Max pointed out there is a hidden cast from int64_t to int.
>>> So use the newly introduced nb_sectors_lun2qemu for all
>>> limits.
>>>
>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>> ---
>>> block/iscsi.c | 20 ++++++++++----------
>>> 1 file changed, 10 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/block/iscsi.c b/block/iscsi.c
>>> index 1ae4add..85131b7 100644
>>> --- a/block/iscsi.c
>>> +++ b/block/iscsi.c
>>> @@ -1468,23 +1468,23 @@ static void
>>> iscsi_refresh_limits(BlockDriverState *bs, Error **errp)
>>> if (iscsilun->lbp.lbpu) {
>>> if (iscsilun->bl.max_unmap < 0xffffffff) {
>>> - bs->bl.max_discard =
>>> sector_lun2qemu(iscsilun->bl.max_unmap,
>>> - iscsilun);
>>> + bs->bl.max_discard =
>>> nb_sectors_lun2qemu(iscsilun->bl.max_unmap,
>>> + iscsilun);
>>> }
>>> - bs->bl.discard_alignment =
>>> sector_lun2qemu(iscsilun->bl.opt_unmap_gran,
>>> - iscsilun);
>>> + bs->bl.discard_alignment =
>>> nb_sectors_lun2qemu(iscsilun->bl.opt_unmap_gran,
>>> + iscsilun);
>>
>> This looks wrong. I think an alignment should always be a power of
>> two. The function however may return the unaligned INT_MAX. I think
>> it should be capped to something like INT_MAX / 2 + 1 or just simply
>> written out 0x40000000.
>
> Good point, I would cap all limits to the highest power of two and use
> INT_MAX / 2 + 1 directly in nb_sectors_lun2qemu?
Seems good enough. I'd just like a comment in that function why you're
doing that (in order to limit both alignments and "normal" lengths
properly).
I'm counting on nobody noticing that INT_MAX may be something different
than 2^x - 1. *g*
Max
> Peter
>
>>
>>> }
>>> if (iscsilun->bl.max_ws_len < 0xffffffff) {
>>> - bs->bl.max_write_zeroes =
>>> sector_lun2qemu(iscsilun->bl.max_ws_len,
>>> - iscsilun);
>>> + bs->bl.max_write_zeroes =
>>> nb_sectors_lun2qemu(iscsilun->bl.max_ws_len,
>>> + iscsilun);
>>> }
>>> if (iscsilun->lbp.lbpws) {
>>> - bs->bl.write_zeroes_alignment =
>>> sector_lun2qemu(iscsilun->bl.opt_unmap_gran,
>>> - iscsilun);
>>> + bs->bl.write_zeroes_alignment =
>>> nb_sectors_lun2qemu(iscsilun->bl.opt_unmap_gran,
>>> + iscsilun);
>>
>> Same here.
>>
>>> }
>>> - bs->bl.opt_transfer_length =
>>> sector_lun2qemu(iscsilun->bl.opt_xfer_len,
>>> - iscsilun);
>>> + bs->bl.opt_transfer_length =
>>> nb_sectors_lun2qemu(iscsilun->bl.opt_xfer_len,
>>> + iscsilun);
>>> }
>>> /* Since iscsi_open() ignores bdrv_flags, there is nothing to do
>>> here in
>>
>> Max
>
>
next prev parent reply other threads:[~2014-10-27 8:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 16:18 [Qemu-devel] [PATCHv5 0/6] introduce max_transfer_length Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 1/6] util: introduce MIN_NON_ZERO Peter Lieven
2014-10-27 8:24 ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 2/6] BlockLimits: introduce max_transfer_length Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 3/6] block/iscsi: set max_transfer_length Peter Lieven
2014-10-27 8:28 ` Max Reitz
2014-10-27 8:36 ` Peter Lieven
2014-10-27 8:44 ` Max Reitz
2014-10-27 8:47 ` Peter Lieven
2014-10-27 9:04 ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 4/6] block: avoid creating oversized writes in multiwrite_merge Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 5/6] block/iscsi: limit to INT_MAX throughout iscsi_refresh_limits Peter Lieven
2014-10-27 8:32 ` Max Reitz
2014-10-27 8:35 ` Peter Lieven
2014-10-27 8:38 ` Max Reitz [this message]
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 6/6] block/iscsi: check for oversized requests Peter Lieven
2014-10-27 8:35 ` Max Reitz
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=544E0493.7060403@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--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).