From: Kevin Wolf <kwolf@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: ronniesahlberg@gmail.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.0] block/nfs: bump libnfs requirement to 1.9.3
Date: Tue, 18 Mar 2014 10:54:24 +0100 [thread overview]
Message-ID: <20140318095424.GI4607@noname.str.redhat.com> (raw)
In-Reply-To: <1395045453-15006-1-git-send-email-pl@kamp.de>
Am 17.03.2014 um 09:37 hat Peter Lieven geschrieben:
> libnfs prior to 1.9.3 contains a bug that will report
> wrong transfer sizes if the file offset grows beyond 4GB
> and RPC responses are received out of order. this
> error is not detectable and fixable in qemu.
>
> additionally 1.9.3 introcudes support for handling short
Fixed while applying: s/introcudes/introduces/
> read/writes in general and takes care of the necessary
> retransmissions internally.
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
Thanks, applied to the block branch for qemu 2.0.
Kevin
parent reply other threads:[~2014-03-18 9:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1395045453-15006-1-git-send-email-pl@kamp.de>]
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=20140318095424.GI4607@noname.str.redhat.com \
--to=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).