From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-stable@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] nbd: Don't trim unrequested bytes
Date: Wed, 25 May 2016 05:25:55 -0600 [thread overview]
Message-ID: <57458BC3.6000606@redhat.com> (raw)
In-Reply-To: <1464173965-9694-1-git-send-email-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
On 05/25/2016 04:59 AM, Eric Blake wrote:
> Similar to commit df7b97ff, we are mishandling clients that
> give an unaligned NBD_CMD_TRIM request, and potentially
> trimming bytes that occur before their request; which in turn
> can cause potential unintended data loss (unlikely in
> practice, since most clients are sane and issue aligned trim
> requests). However, while we fixed read and write by switching
> to the byte interfaces of blk_, we don't yet have a byte
> interface for discard. On the other hand, trim is advisory, so
> rounding the user's request to simply ignore the first and last
> unaligned sectors (or the entire request, if it is sub-sector
> in length) is just fine.
>
> CC: qemu-stable@nongnu.org
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> v2: don't underflow request.len on sub-sector requests
>
> nbd/server.c | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/nbd/server.c b/nbd/server.c
> index fa862cd..b2cfeb9 100644
> --- a/nbd/server.c
> +++ b/nbd/server.c
> @@ -1153,12 +1153,20 @@ static void nbd_trip(void *opaque)
> break;
> case NBD_CMD_TRIM:
> TRACE("Request type is TRIM");
> - ret = blk_co_discard(exp->blk, (request.from + exp->dev_offset)
> - / BDRV_SECTOR_SIZE,
> - request.len / BDRV_SECTOR_SIZE);
> - if (ret < 0) {
> - LOG("discard failed");
> - reply.error = -ret;
> + /* Ignore unaligned head or tail, until block layer adds byte
> + * interface */
> + if (request.len >= BDRV_SECTOR_SIZE) {
> + request.len -= (request.from + request.len) % BDRV_SECTOR_SIZE;
> + ret = blk_co_discard(exp->blk,
> + DIV_ROUND_UP(request.from + exp->dev_offset,
> + BDRV_SECTOR_SIZE),
> + request.len / BDRV_SECTOR_SIZE);
This can end up calling blk_co_discard(, , 0) - do we need to audit
whether all underlying drivers handle a 0-length request, and/or
special-case this in blk_co_discard() to be an explicit no-op?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-05-25 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 10:59 [Qemu-devel] [PATCH v2] nbd: Don't trim unrequested bytes Eric Blake
2016-05-25 11:25 ` Eric Blake [this message]
2016-05-25 12:33 ` 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=57458BC3.6000606@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.