From: Greg Kurz <groug@kaod.org>
To: jiangyiwen <jiangyiwen@huawei.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
v9fs-developer@lists.sourceforge.net, qemu-devel@nongnu.org,
aneesh.kumar@linux.vnet.ibm.com,
Ron Minnich <rminnich@sandia.gov>,
Latchesar Ionkov <lucho@ionkov.net>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Veaceslav Falico <veaceslav.falico@huawei.com>
Subject: Re: [Qemu-devel] [V9fs-developer] [RFC] we should solve create-unlink-getattr idiom
Date: Fri, 9 Feb 2018 12:33:42 +0100 [thread overview]
Message-ID: <20180209123342.11b17062@bahia.lan> (raw)
In-Reply-To: <5A7D4976.6060407@huawei.com>
On Fri, 9 Feb 2018 15:10:46 +0800
jiangyiwen <jiangyiwen@huawei.com> wrote:
> Hi Eric and Greg,
>
> I encountered the similar problem with create-unlink-getattr idiom.
> I use the testcase that create-unlink-setattr idiom, and I see the
> bug is reported at https://bugs.launchpad.net/qemu/+bug/1336794.
> Then I also see you already fix the issue and push the patch to upstream.
> https://github.com/ericvh/linux/commit/eaf70223eac094291169f5a6de580351890162a2
> http://patchwork.ozlabs.org/patch/626194/
>
> Unfortunately, the two patches are not merged into master, I don't know
> the reason, so I suggest if the patche can be merged into master, and
> it will solve the create-unlink-getattr idiom.
>
I had tried to go a bit further and address the general issue of f*() syscalls
versus unlinked files:
QEMU:
http://lists.gnu.org/archive/html/qemu-devel/2016-06/msg07586.html
Linux 9p driver:
https://sourceforge.net/p/v9fs/mailman/message/35175775/
I remember that some issues were then reported during review of the
linux patches, and I never got bandwidth to investigate further...
But if you'd like to resurrect these threads, please do. :)
> Thanks,
> Yiwen
>
Cheers,
--
Greg
next prev parent reply other threads:[~2018-02-09 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 7:10 [Qemu-devel] [V9fs-developer] [RFC] we should solve create-unlink-getattr idiom jiangyiwen
2018-02-09 7:21 ` Veaceslav Falico
2018-02-09 11:49 ` Greg Kurz
2018-02-09 11:33 ` Greg Kurz [this message]
2018-02-11 2:33 ` jiangyiwen
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=20180209123342.11b17062@bahia.lan \
--to=groug@kaod.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ericvh@gmail.com \
--cc=jiangyiwen@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=qemu-devel@nongnu.org \
--cc=rminnich@sandia.gov \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=veaceslav.falico@huawei.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).