From: Greg Kurz <groug@kaod.org>
To: Veaceslav Falico <veaceslav.falico@huawei.com>
Cc: jiangyiwen <jiangyiwen@huawei.com>,
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
Subject: Re: [Qemu-devel] [V9fs-developer] [RFC] we should solve create-unlink-getattr idiom
Date: Fri, 9 Feb 2018 12:49:22 +0100 [thread overview]
Message-ID: <20180209124922.3a215c34@bahia.lan> (raw)
In-Reply-To: <a1ef7be5-d368-fe31-4386-1d40762b5849@huawei.com>
On Fri, 9 Feb 2018 08:21:52 +0100
Veaceslav Falico <veaceslav.falico@huawei.com> wrote:
> Hi Yiwen, all,
>
> On 2/9/2018 8:10 AM, jiangyiwen 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.
>
> As a follow up - the create-unlink-setattr (mainly ftruncate and anything
> else which works on fd instead of path) isn't fixed by these patches, but
> I'm currently working on a new patch, obviously on top of those two, to
> make the setattr work too.
>
> It's based on the same logic as the above patches though - use FIDs with
> open fd's guest side and use open fd's host side if possible with f*
> functions, otherwise path with l* functions.
>
> It's bigger than the QEMU getattr patch, as there are no f* functions
> available for ftruncate case, for example.
>
As I was saying to Yiwen, maybe have a look at:
https://github.com/gkurz/qemu/commits/9p-attr-fixes
It is probably too old to rebase cleanly on current master, but it gives
the general idea.
IIRC, the cause for this not moving forward was because of an issue
unveiled/introduced by patch 3/3 in the linux 9p driver:
https://sourceforge.net/p/v9fs/mailman/v9fs-developer/thread/20160704141655.GA5799%40u-isr-cdi-08/#msg35199720
and a general lack of care for the 9p code at the time... but it seems
you guys are willing to go forward, and that's cool ! :)
Cheers,
--
Greg
> So if those two patches could be merged it'd be a lot easier to then
> go forward with the setattr fix.
>
> Thank you!
>
> >
> > Thanks,
> > Yiwen
> >
> > .
> >
>
>
next prev parent reply other threads:[~2018-02-09 11:56 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 [this message]
2018-02-09 11:33 ` Greg Kurz
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=20180209124922.3a215c34@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).