From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Qemu Development List <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu 9p mapped-xattr model does not translate d_type in readdir
Date: Wed, 20 Aug 2014 16:22:51 +0530 [thread overview]
Message-ID: <87a96zsa9o.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <53EBBF5F.3070805@msgid.tls.msk.ru>
Michael Tokarev <mjt@tls.msk.ru> writes:
> There's another bugreport filed against debian qemu package,
> http://bugs.debian.org/755738 . It talks about security_model=mapped-xattr
> case, where file type is stored elsewhere, and all files are turned into
> regular files. http://bugs.debian.org/755738#10 is the proposed patch.
>
Ok the patch looks good, we could also try to get the d_type correct by
looking at the xattr mode bits, but i guess that will slow down readdir
Can you send a proper patch with signed-off-by to the list. I will pick
it from there.
-aneesh
prev parent reply other threads:[~2014-08-20 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 19:41 [Qemu-devel] qemu 9p mapped-xattr model does not translate d_type in readdir Michael Tokarev
2014-08-20 10:52 ` Aneesh Kumar K.V [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=87a96zsa9o.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=Qemu-devel@nongnu.org \
--cc=mjt@tls.msk.ru \
/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).