qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	supriyak@linux.vnet.ibm.com, eblake@redhat.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 15/19] block: raw-win32 driver reopen support
Date: Fri, 21 Sep 2012 08:17:04 -0400	[thread overview]
Message-ID: <505C5AC0.5090500@redhat.com> (raw)
In-Reply-To: <505C28C1.2090609@redhat.com>

On 09/21/2012 04:43 AM, Paolo Bonzini wrote:
> Il 21/09/2012 10:33, Kevin Wolf ha scritto:
>>>> +    /* could not reopen the file handle, so fall back to opening
>>>> +     * new file (CreateFile) */
>>>> +    if (raw_s->hfile == INVALID_HANDLE_VALUE) {
>>>> +        raw_s->hfile = CreateFile(state->bs->filename, access_flags,
>>>> +                                  FILE_SHARE_READ, NULL, OPEN_EXISTING,
>>>> +                                  overlapped, NULL);
>>>> +        if (raw_s->hfile == INVALID_HANDLE_VALUE) {
>>>> +            /* this could happen because the access_flags requested are
>>>> +             * incompatible with the existing share mode of s->hfile,
>>>> +             * so our only option now is to close s->hfile, and try again.
>>>> +             * This could end badly */
>>>> +            CloseHandle(s->hfile);
>> How common is this case?
>>
>> We do have another option, namely not reopen at all and return an error.
>> Of course, this only makes sense if it doesn't mean that we almost never
>> succeed.
> 
> Probably pretty common since we specify FILE_SHARE_READ for the sharing
> mode, meaning that "subsequent open operations on a file or device are
> only able to request read access".
> 

Yes, I think this is by far the most common case.


> I would change it to FILE_SHARE_READ|FILE_SHARE_WRITE and remove this code.
> 
> Paolo
> 

I contemplated doing that, but I wasn't sure if there was any particular
reason it was originally done with FILE_SHARE_READ only in the first
place (security, etc..). I was hesitant to override that behaviour as
the new default under w32.  Do we know if this is acceptable / safe?

  reply	other threads:[~2012-09-21 12:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 19:13 [Qemu-devel] [PATCH v4 00/19] block: bdrv_reopen() patches Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 01/19] block: correctly set the keep_read_only flag Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 02/19] block: make bdrv_set_enable_write_cache() modify open_flags Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 03/19] block: Framework for reopening files safely Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 04/19] block: move aio initialization into a helper function Jeff Cody
2012-09-21 10:03   ` Kevin Wolf
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 05/19] block: move open flag parsing in raw block drivers to helper functions Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 06/19] block: do not parse BDRV_O_CACHE_WB in block drivers Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 07/19] block: use BDRV_O_NOCACHE instead of s->aligned_buf in raw-posix.c Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 08/19] block: purge s->aligned_buf and s->aligned_buf_size from raw-posix.c Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 09/19] block: raw-posix image file reopen Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 10/19] block: raw " Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 11/19] block: qed " Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 12/19] block: qcow2 " Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 13/19] block: qcow " Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 14/19] block: vmdk " Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 15/19] block: raw-win32 driver reopen support Jeff Cody
2012-09-21  8:33   ` Kevin Wolf
2012-09-21  8:43     ` Paolo Bonzini
2012-09-21 12:17       ` Jeff Cody [this message]
2012-09-21 12:31         ` Paolo Bonzini
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 16/19] block: vdi image file reopen Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 17/19] block: vpc " Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 18/19] block: convert bdrv_commit() to use bdrv_reopen() Jeff Cody
2012-09-20 19:13 ` [Qemu-devel] [PATCH v4 19/19] block: remove keep_read_only flag from BlockDriverState struct Jeff Cody
2012-09-21 10:39 ` [Qemu-devel] [PATCH v4 00/19] block: bdrv_reopen() patches 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=505C5AC0.5090500@redhat.com \
    --to=jcody@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=supriyak@linux.vnet.ibm.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).