From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Gabriel de Perthuis <g2p.code@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] 9p: Be robust against paths without FS_IOC_GETVERSION
Date: Fri, 10 May 2013 09:00:32 +0530 [thread overview]
Message-ID: <87r4hfo6jr.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <518AE484.9090204@gmail.com>
Gabriel de Perthuis <g2p.code@gmail.com> writes:
> The current implementation checked for supported filesystems at mount
> time, but actual support depends on the path. Don't error out when
> finding unversioned paths.
Can you elaborate this a bit ?
>
> This fix allows booting a linux kernel with the same / filesystem as the
> host; otherwise the boot fails when mounting devtmpfs.
>
> Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
> ---
> hw/9pfs/cofile.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/9pfs/cofile.c b/hw/9pfs/cofile.c
> index 2efebf3..194c130 100644
> --- a/hw/9pfs/cofile.c
> +++ b/hw/9pfs/cofile.c
> @@ -36,10 +36,14 @@ int v9fs_co_st_gen(V9fsPDU *pdu, V9fsPath *path, mode_t st_mode,
> err = -errno;
> }
> });
> v9fs_path_unlock(s);
> }
> + /* The ioctl may not be supported depending on the path */
> + if (err == -ENOTTY) {
> + err = 0;
> + }
So you don't want to consider -ENOTTY as an error ? why ?
> return err;
> }
>
> int v9fs_co_lstat(V9fsPDU *pdu, V9fsPath *path, struct stat *stbuf)
> {
> --
-aneesh
next prev parent reply other threads:[~2013-05-10 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 23:49 [Qemu-devel] [PATCH] 9p: Be robust against paths without FS_IOC_GETVERSION Gabriel de Perthuis
2013-05-10 3:30 ` Aneesh Kumar K.V [this message]
2013-05-10 6:42 ` Gabriel de Perthuis
2013-05-10 10:38 ` Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2013-05-10 17:53 Gabriel de Perthuis
2013-05-08 23:33 Gabriel de Perthuis
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=87r4hfo6jr.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=g2p.code@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).