From: Michael Tokarev <mjt@tls.msk.ru>
To: "M. Mohan Kumar" <mohan@in.ibm.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 9pfs: unWRITAble dirs with random errors in guest
Date: Sun, 19 May 2013 20:12:54 +0400 [thread overview]
Message-ID: <5198FA06.1000802@msgid.tls.msk.ru> (raw)
In-Reply-To: <87obf4z6xs.fsf@in.ibm.com>
Rehashing an old thread again...
28.02.2013 21:25, M. Mohan Kumar wrote:
> Michael Tokarev <mjt@tls.msk.ru> writes:
>
>
>> 28.02.2013 17:55, M. Mohan Kumar wrote:
>>> Michael Tokarev <mjt@tls.msk.ru> writes:
>>>
>>> Hi,
>>>
>>> Please try mounting with -oversion=9p2000.L
>>>
>>> With qemu-1.4.0 and 9p2000.L, I could not recreate this issue. ie not
>>> getting Unknown error during directory listing.
>>
>> Yes, with 9p2000.L it works fine, both reported
>> issues are gone.
>>
>>> I am using Guest kernel 3.8.0-rc5+.
>>
>> But do you see my original error, with the default mount version?
>> (I'm using 3.2 guest kernel if that matters, and it is also 32bits,
>> which should not matter).
> Yes, with default mount option, i am getting same error.
So, is there any intention to fix that for the default mount
options? Or should the corresponding protocol be just marked
as broken and qemu to refuse its usage? I think it is either
one or another, -- either fix or drop, that is, keeping
known-broken behavor isn't exactly the right thing.
Thanks,
/mjt
>>>> When I mount a 9pfs filesystem in guest with no write permission for
>>>> some dirs, I'm getting strange errors in guest.
>>>>
>>>> Host (as a regular user):
>>>> qemu-system-x86_64 -virtfs local,path=/,security_model=mapped-file,mount_tag=tag
>>>>
>>>> Guest:
>>>> # mount -t 9p -o trans=virtio,ro tag /mnt
>>>> # ls /mnt
>>>> ls: reading directory /mnt: Unknown error 593
>>>> # ls /mnt/dev
>>>> ls: reading directory /mnt/dev: Unknown error 849
>>>> # ls /mnt/tmp
>>>> [works]
>>>> # ls /mnt/root
>>>> ls: cannot open directory /mnt/root: Permission denied
>>>>
>>>> So, it reports errors while trying to _read_ (not open)
>>>> readable but non-writable dirs, and these errors are _random_.
>>>> It correctly reports errors when trying to open an unreadable
>>>> dir.
>>>>
>>>> This is 1.4.0. Similar problem exists with earlier versions
>>>> of qemu.
>>>>
>>>> Thanks!
>>>>
>>>> /mjt
>>>
>
>
next parent reply other threads:[~2013-05-19 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512EF3A0.5010007@msgid.tls.msk.ru>
[not found] ` <87r4k0zgo1.fsf@in.ibm.com>
[not found] ` <512F677E.2060403@msgid.tls.msk.ru>
[not found] ` <87obf4z6xs.fsf@in.ibm.com>
2013-05-19 16:12 ` Michael Tokarev [this message]
2013-05-20 10:03 ` [Qemu-devel] 9pfs: unWRITAble dirs with random errors in guest Aneesh Kumar K.V
2013-05-20 17:31 ` Aneesh Kumar K.V
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=5198FA06.1000802@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=mohan@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.