From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Justin Ossevoort <justin@quarantainenet.nl>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/2] qga/commands-posix: Fix bug in guest-fstrim
Date: Tue, 26 May 2015 19:50:10 -0500 [thread overview]
Message-ID: <20150527005010.5594.20483@loki> (raw)
In-Reply-To: <1431327525-25625-2-git-send-email-justin@quarantainenet.nl>
Quoting Justin Ossevoort (2015-05-11 01:58:44)
> The FITRIM ioctl updates the fstrim_range structure it receives. This
> way the caller can determine how many bytes were trimmed. The
> guest-fstrim logic reuses the same fstrim_range for each filesystem,
> effectively limiting each filesystem to trim at most as much as the
> previous was able to trim.
>
> If a previous filesystem would have trimmed 0 bytes, than the next
> filesystem would report an error 'Invalid argument' because a FITRIM
> request with length 0 is not valid.
>
> This change resets the fstrim_range structure for each filesystem.
>
> Signed-off-by: Justin Ossevoort <justin@quarantainenet.nl>
Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc'ing qemu-stable@nongnu.org
> ---
> qga/commands-posix.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> index ba8de62..4449628 100644
> --- a/qga/commands-posix.c
> +++ b/qga/commands-posix.c
> @@ -1332,11 +1332,7 @@ void qmp_guest_fstrim(bool has_minimum, int64_t minimum, Error **errp)
> struct FsMount *mount;
> int fd;
> Error *local_err = NULL;
> - struct fstrim_range r = {
> - .start = 0,
> - .len = -1,
> - .minlen = has_minimum ? minimum : 0,
> - };
> + struct fstrim_range r;
>
> slog("guest-fstrim called");
>
> @@ -1360,6 +1356,9 @@ void qmp_guest_fstrim(bool has_minimum, int64_t minimum, Error **errp)
> * error means an unexpected error, so return it in those cases. In
> * some other cases ENOTTY will be reported (e.g. CD-ROMs).
> */
> + r.start = 0;
> + r.len = -1;
> + r.minlen = has_minimum ? minimum : 0;
> ret = ioctl(fd, FITRIM, &r);
> if (ret == -1) {
> if (errno != ENOTTY && errno != EOPNOTSUPP) {
> --
> 2.1.4
>
>
next prev parent reply other threads:[~2015-05-27 0:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 6:58 [Qemu-devel] [PATCH v4 0/2] Fix guest-fstrim behaviour Justin Ossevoort
2015-05-11 6:58 ` [Qemu-devel] [PATCH v4 1/2] qga/commands-posix: Fix bug in guest-fstrim Justin Ossevoort
2015-05-26 18:54 ` Thomas Huth
2015-05-27 0:50 ` Michael Roth [this message]
2015-05-11 6:58 ` [Qemu-devel] [PATCH v4 2/2] qga/qmp_guest_fstrim: Return per path fstrim result Justin Ossevoort
2015-05-25 10:41 ` Olga Krishtal
2015-05-27 1:20 ` Michael Roth
2015-05-27 4:13 ` Michael Roth
2015-05-27 4:25 ` Eric Blake
2015-07-07 1:32 ` [Qemu-devel] [PATCH v4 0/2] Fix guest-fstrim behaviour Michael Roth
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=20150527005010.5594.20483@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=justin@quarantainenet.nl \
--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 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).