From: John Snow <jsnow@redhat.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] ide: abort TRIM operation for invalid range
Date: Fri, 8 Dec 2017 15:13:25 -0500 [thread overview]
Message-ID: <79b1b330-74b2-980a-e2db-4c24f3a1f4fc@redhat.com> (raw)
In-Reply-To: <1512735034-35327-1-git-send-email-anton.nefedov@virtuozzo.com>
On 12/08/2017 07:10 AM, Anton Nefedov wrote:
> Started from the separate series discussion (trim statistics) , see
> http://lists.nongnu.org/archive/html/qemu-devel/2017-12/msg01059.html
>
> There is no range check for IDE trim requests now.
> Such request will likely be rejected by the block layer and count as
> failed and not an invalid/aborted operation.
>
> Anton Nefedov (3):
> ide: pass IDEState to trim AIO callback
> ide: move ide_sect_range_ok() up
> ide: abort TRIM operation for invalid range
>
> hw/ide/core.c | 53 +++++++++++++++++++++++++++++++++--------------------
> 1 file changed, 33 insertions(+), 20 deletions(-)
>
Thanks, applied to my IDE tree:
https://github.com/jnsnow/qemu/commits/ide
https://github.com/jnsnow/qemu.git
--js
(PR won't be sent until after the 2.12 tree opens.)
next prev parent reply other threads:[~2017-12-08 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 12:10 [Qemu-devel] [PATCH 0/3] ide: abort TRIM operation for invalid range Anton Nefedov
2017-12-08 12:10 ` [Qemu-devel] [PATCH 1/3] ide: pass IDEState to trim AIO callback Anton Nefedov
2017-12-08 12:10 ` [Qemu-devel] [PATCH 2/3] ide: move ide_sect_range_ok() up Anton Nefedov
2017-12-08 12:10 ` [Qemu-devel] [PATCH 3/3] ide: abort TRIM operation for invalid range Anton Nefedov
2017-12-08 19:51 ` John Snow
2017-12-11 8:38 ` Anton Nefedov
2017-12-08 20:13 ` John Snow [this message]
2018-01-19 22:31 ` [Qemu-devel] [PATCH 0/3] " John Snow
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=79b1b330-74b2-980a-e2db-4c24f3a1f4fc@redhat.com \
--to=jsnow@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=qemu-block@nongnu.org \
--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).