From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: Jianyong Wu <jianyong.wu@arm.com>, <ericvh@gmail.com>,
<lucho@ionkov.net>, <asmadeus@codewreck.org>,
<v9fs-developer@lists.sourceforge.net>, <justin.he@arm.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [V9fs-developer] [PATCH RFC 0/4] 9p: fix open-unlink-f*syscall bug
Date: Mon, 14 Sep 2020 14:43:25 +0200 [thread overview]
Message-ID: <20200914144325.7928dbd3@bahia.lan> (raw)
In-Reply-To: <2828347.d8MXItvaOC@silver>
On Mon, 14 Sep 2020 13:06:34 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> On Montag, 14. September 2020 10:35:46 CEST Greg Kurz wrote:
> > On Mon, 14 Sep 2020 11:37:50 +0800
> >
> > Jianyong Wu <jianyong.wu@arm.com> wrote:
> > > open-unlink-f*syscall bug is a well-known bug in 9p, we try to fix the bug
> > > in this patch set.
> > > I take Eric's and Greg's patches which constiute the 1/4 - 3/4 of this
> > > patch set as the main frame of the solution. In patch 4/4, I fix the fid
> > > race issue exists in Greg's patch.
> >
> > IIRC some patches were needed on the QEMU side as well... I'm spending
> > less time on 9pfs in QEMU, so Cc'ing the new maintainer:
> >
> > Christian Schoenebeck <qemu_oss@crudebyte.com>
>
> AFAICS this is about this old bug report:
> https://bugs.launchpad.net/qemu/+bug/1336794
>
Correct.
> So yes, looks like this also requires changes to the 9pfs 'local' fs driver on
> QEMU side:
> https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg07586.html
>
> Eric, Greg, would there be an easy way to establish QEMU test cases running
> the 9pfs 'local' fs driver? Right now we only have 9pfs qtest cases for QEMU
> which can only use the 'synth' driver, which is not helpful for such kind of
> issues.
>
I guess it's possible to introduce new qtests that start QEMU with
-fsdev local instead of -fsdev synth... I haven't looked in a while
though, so I won't comment on "easy way" ;-)
> Best regards,
> Christian Schoenebeck
>
>
next prev parent reply other threads:[~2020-09-14 13:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 3:37 [PATCH RFC 0/4] 9p: fix open-unlink-f*syscall bug Jianyong Wu
2020-09-14 3:37 ` [PATCH RFC 1/4] fs/9p: fix create-unlink-getattr idiom Jianyong Wu
2020-09-14 6:00 ` Dominique Martinet
2020-09-14 8:11 ` Greg Kurz
2020-09-14 3:37 ` [PATCH RFC 2/4] fs/9p: track open fids Jianyong Wu
2020-09-14 3:37 ` [PATCH RFC 3/4] fs/9p: search open fids first Jianyong Wu
2020-09-14 3:37 ` [PATCH RFC 4/4] 9p: fix race issue in fid contention Jianyong Wu
2020-09-14 5:55 ` Dominique Martinet
2020-09-14 6:31 ` [V9fs-developer] " Dominique Martinet
2020-09-14 7:50 ` Jianyong Wu
2020-09-14 7:32 ` Jianyong Wu
2020-09-14 8:32 ` Dominique Martinet
2020-09-14 12:34 ` Jianyong Wu
2020-09-18 8:57 ` Jianyong Wu
2020-09-18 9:34 ` Dominique Martinet
2020-09-18 10:05 ` Jianyong Wu
2020-09-14 8:35 ` [V9fs-developer] [PATCH RFC 0/4] 9p: fix open-unlink-f*syscall bug Greg Kurz
2020-09-14 11:06 ` Christian Schoenebeck
2020-09-14 12:43 ` Greg Kurz [this message]
2020-09-14 15:19 ` Christian Schoenebeck
2020-09-14 15:46 ` Greg Kurz
2020-09-16 12:16 ` Greg Kurz
2020-09-17 10:07 ` Christian Schoenebeck
2020-09-14 12:36 ` Jianyong Wu
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=20200914144325.7928dbd3@bahia.lan \
--to=groug@kaod.org \
--cc=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=jianyong.wu@arm.com \
--cc=justin.he@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=qemu_oss@crudebyte.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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