From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, Bastian Blank <waldi@debian.org>
Subject: Re: [Qemu-devel] Don't return type from host in readdir on local 9p filesystem
Date: Wed, 03 Sep 2014 16:39:35 -0500 [thread overview]
Message-ID: <87sik8e63s.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1408699341-6126-1-git-send-email-mjt@msgid.tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> writes:
> From: Bastian Blank <waldi@debian.org>
>
> When using mapped mode in 9pfs, readdir implementation
> should not return file type in d_type from the host
> readdir, instead, it should use the type stored in
> the extended attributes. Since d_type is optional
> and reading ext attrs for every readdir is expensive,
> it should be sufficient to just set d_type to DT_UNKNOWN,
> so guest will know to look it up separately.
>
> This is a -stable material.
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
>
> --- qemu-2.0.0+dfsg.orig/hw/9pfs/virtio-9p-local.c
> +++ qemu-2.0.0+dfsg/hw/9pfs/virtio-9p-local.c
> @@ -396,12 +396,16 @@ static int local_readdir_r(FsContext *ct
>
> again:
> ret = readdir_r(fs->dir, entry, result);
> - if (ctx->export_flags & V9FS_SM_MAPPED_FILE) {
> + if (ctx->export_flags & V9FS_SM_MAPPED) {
> + entry->d_type = DT_UNKNOWN;
> + }
> + else if (ctx->export_flags & V9FS_SM_MAPPED_FILE) {
> if (!ret && *result != NULL &&
> !strcmp(entry->d_name, VIRTFS_META_DIR)) {
> /* skp the meta data directory */
> goto again;
> }
> + entry->d_type = DT_UNKNOWN;
> }
> return ret;
> }
Hi Bastian,
Can I add your signed-off-by to this patch ?
-aneesh
next prev parent reply other threads:[~2014-09-03 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 9:22 [Qemu-devel] Don't return type from host in readdir on local 9p filesystem Michael Tokarev
2014-09-03 21:39 ` Aneesh Kumar K.V [this message]
2014-09-04 13:24 ` Bastian Blank
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=87sik8e63s.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=waldi@debian.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).