From: Stefan Hajnoczi <stefanha@gmail.com>
To: mohan@in.ibm.com
Cc: rlandley@parallels.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC/PATCH] virtio-9p: Add Read only support for 9p export.
Date: Mon, 23 May 2011 14:17:18 +0100 [thread overview]
Message-ID: <BANLkTimoYAskzJN2frzc3hv72W3VQLJLPA@mail.gmail.com> (raw)
In-Reply-To: <20110523114912.GA26653@in.ibm.com>
On Mon, May 23, 2011 at 12:49 PM, M. Mohan Kumar <mohan@in.ibm.com> wrote:
> On Mon, May 23, 2011 at 11:08:34AM +0100, Stefan Hajnoczi wrote:
>> On Mon, May 23, 2011 at 8:58 AM, M. Mohan Kumar <mohan@in.ibm.com> wrote:
>> > A new fsdev parameter "access" is introduced to control accessing 9p export.
>> > access=ro|rw can be used to specify the access type. By default rw access
>> > is given to 9p export.
>>
>> It would be consistent with -drive to use readonly=on|off (default:
>> off). Do you have any future access modes in mind that require more
>> than readonly on|off?
>
> You mean to use 'readonly=on|off' instead of 'access=ro|rw' ?
Yes.
>
>>
>> It seems the client does not know ahead of time that the mount is
>> read-only. I wonder if this exposes any weirdness compared to
>> actually mounting ro on the client side (i.e. operations that appear
>> to start okay but then fail with -EROFS at a different point than if
>> you had mounted ro)? It could cause apps to error in new ways.
>>
>
> When a NFS share is exported as read-only, client will come to know about
> that when it does some write operation. IMHO its not an issue.
If it works the same way on NFS then great.
Stefan
prev parent reply other threads:[~2011-05-23 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 7:58 [Qemu-devel] [RFC/PATCH] virtio-9p: Add Read only support for 9p export M. Mohan Kumar
2011-05-23 10:08 ` Stefan Hajnoczi
2011-05-23 11:49 ` M. Mohan Kumar
2011-05-23 13:17 ` Stefan Hajnoczi [this message]
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=BANLkTimoYAskzJN2frzc3hv72W3VQLJLPA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=mohan@in.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rlandley@parallels.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).