qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlhnet.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH 3/3] iscsi_truncate: ensure there are no requests in flight
Date: Mon, 11 Mar 2013 12:52:01 +0100	[thread overview]
Message-ID: <513DC561.7080802@dlhnet.de> (raw)
In-Reply-To: <513DC3AF.8030104@redhat.com>

On 11.03.2013 12:44, Paolo Bonzini wrote:
> Il 11/03/2013 11:19, Peter Lieven ha scritto:
>>
>> Am 11.03.2013 um 11:16 schrieb Paolo Bonzini <pbonzini@redhat.com>:
>>
>>> Il 11/03/2013 11:05, Peter Lieven ha scritto:
>>>> ensure that there are no pending I/Os before calling
>>>> the sync readcapacity commands. the block_resize monitor
>>>> command will also flush all I/O, but double check in
>>>> case iscsi_truncate() is called from elsewhere in the
>>>> future.
>>>>
>>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>>> ---
>>>> block/iscsi.c |    4 ++++
>>>> 1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/block/iscsi.c b/block/iscsi.c
>>>> index 3d52921..de20d53 100644
>>>> --- a/block/iscsi.c
>>>> +++ b/block/iscsi.c
>>>> @@ -1167,6 +1167,10 @@ static int iscsi_truncate(BlockDriverState *bs,
>>>> int64_t offset)
>>>>          return -ENOTSUP;
>>>>      }
>>>>
>>>> +    /* ensure all async requests are completed before executing
>>>> +     * a sync readcapacity */
>>>> +    bdrv_drain_all();
>>>> +
>>>>      if ((ret = iscsi_readcapacity_sync(iscsilun)) != 0) {
>>>>          return ret;
>>>>      }
>>>
>>> NACK to this patch.  It would be a bug, let's fix it properly.
>>
>> ok, are you sure that never ever will some new feature call bdrv_truncate() on an iscsi
>> device?
>
> I'm sure some new feature _will_ call bdrv_truncate().  But as things
> stand now, it would be a bug to do so on an iSCSI device.
>
> For example, qcow1 (and VHDX) will already call it, but that's a bug and
> should be fixed otherwise.  Your patch will just cause an assertion failure.

In which case can qcow1 (and VHDX) be used in conjunction with an iSCSI Target?

Would it be ok for you to assert if iscsi_truncate() is called when there
are aio's in flight? How can this be checked?

I just want to make sure that nothing nasty happens in that case (such as
nested event loops).

Peter

>
> Paolo
>
>> otherwise the real fix would be to implement async read capacity commands like it
>> the first patch version for iscsi_truncate().
>>
>> Peter
>>
>>
>>>
>>> The other two are fine, however.
>>>
>>> Paolo
>>
>

  reply	other threads:[~2013-03-11 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 10:05 [Qemu-devel] [PATCH 3/3] iscsi_truncate: ensure there are no requests in flight Peter Lieven
2013-03-11 10:16 ` Paolo Bonzini
2013-03-11 10:19   ` Peter Lieven
2013-03-11 11:44     ` Paolo Bonzini
2013-03-11 11:52       ` Peter Lieven [this message]
2013-03-11 13:00         ` Paolo Bonzini
2013-03-13  9:31         ` Kevin Wolf
2013-03-13 10:15           ` Paolo Bonzini
2013-03-19  7:29   ` Peter Lieven
2013-03-19  9:44     ` Paolo Bonzini

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=513DC561.7080802@dlhnet.de \
    --to=pl@dlhnet.de \
    --cc=anthony@codemonkey.ws \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).