From: Kevin Wolf <kwolf@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: "Denis V. Lunev" <den@openvz.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] nbd: fix max_discard/max_transfer_length
Date: Fri, 6 Feb 2015 13:48:34 +0100 [thread overview]
Message-ID: <20150206124834.GD13081@noname.redhat.com> (raw)
In-Reply-To: <54D4B0B3.10107@kamp.de>
Am 06.02.2015 um 13:16 hat Peter Lieven geschrieben:
> Am 06.02.2015 um 12:53 schrieb Kevin Wolf:
> > Am 06.02.2015 um 12:24 hat Denis V. Lunev geschrieben:
> >> nbd_co_discard calls nbd_client_session_co_discard which uses uint32_t
> >> as the length in bytes of the data to discard due to the following
> >> definition:
> >>
> >> struct nbd_request {
> >> uint32_t magic;
> >> uint32_t type;
> >> uint64_t handle;
> >> uint64_t from;
> >> uint32_t len; <-- the length of data to be discarded, in bytes
> >> } QEMU_PACKED;
> >>
> >> Thus we should limit bl_max_discard to UINT32_MAX >> BDRV_SECTOR_BITS to
> >> avoid overflow.
> >>
> >> NBD read/write code uses the same structure for transfers. Fix
> >> max_transfer_length accordingly.
> >>
> >> Signed-off-by: Denis V. Lunev <den@openvz.org>
> >> CC: Peter Lieven <pl@kamp.de>
> >> CC: Kevin Wolf <kwolf@redhat.com>
> > Thanks, I have applied both Peter's and your patch. Can you guys please
> > check whether the current state of my block branch is correct or whether
> > I forgot to include or remove some patch?
>
> Looks good from my point of view.
>
> Just to be sure has it to be
>
> if (size > BDRV_REQUEST_MAX_SECTORS << BDRV_SECTOR_BITS)
>
> or
>
> if (size > (BDRV_REQUEST_MAX_SECTORS << BDRV_SECTOR_BITS))
>
> ?
>
> If the latter is right, can you please fix that line in my patch. I am afk now.
Both versions are correct.
Kevin
next prev parent reply other threads:[~2015-02-06 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 10:54 [Qemu-devel] [PATCH V2] block: introduce BDRV_REQUEST_MAX_SECTORS Peter Lieven
2015-02-06 11:24 ` [Qemu-devel] [PATCH 1/1] nbd: fix max_discard/max_transfer_length Denis V. Lunev
2015-02-06 11:53 ` Kevin Wolf
2015-02-06 11:59 ` Denis V. Lunev
2015-02-06 12:01 ` Peter Lieven
2015-02-06 12:07 ` Kevin Wolf
2015-02-06 12:17 ` Denis V. Lunev
2015-02-06 12:22 ` Peter Lieven
2015-02-06 12:24 ` Denis V. Lunev
2015-02-06 12:16 ` Peter Lieven
2015-02-06 12:48 ` Kevin Wolf [this message]
2015-02-06 11:24 ` [Qemu-devel] [PATCH V2] block: introduce BDRV_REQUEST_MAX_SECTORS Denis V. Lunev
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=20150206124834.GD13081@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.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).