From: Dominique Martinet <asmadeus@codewreck.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: Jianyong Wu <jianyong.wu@arm.com>,
ericvh@gmail.com, lucho@ionkov.net, groug@kaod.org,
v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, justin.he@arm.com
Subject: Re: [PATCH RFC v2 4/4] 9p: fix race issue in fid contention.
Date: Wed, 4 Nov 2020 12:57:08 +0100 [thread overview]
Message-ID: <20201104115708.GA30104@nautica> (raw)
In-Reply-To: <1755303.6a88tIVZ8j@silver>
Christian Schoenebeck wrote on Wed, Nov 04, 2020:
> > Greg, Christian - from what I understood (in private, hopefully I'm
> > allowed to repeat!), he won't be able to contribute to qemu because of
> > company policies and I'm unlikely to take the time either right now.
> > I don't think it's a problem to continue as is though, we can land linux
> > kernel support (it's still useful for non-qemu servers) and if someone
> > is interested later on they'll just need to finish that bit.
>
> Hmm, no idea what kind of policy that is; there is no GPL3 in qemu at least
> that some companies are concerned about, but OK not my business.
>
> I actually thought this would still take a while on kernel side,
To be honest, so did I -- the original patches are so old I had more or
less given up on it :P
But I don't see any more problem now and we'll want to get there
eventually so now's a good time as any... I just want to get fault
injection to work to test various refcounting cornercases but shouldn't
be much longer.
> so in the
> meantime we layed the ground in qemu for resolving this issue independent of
> clients and independent of any guest OS installation by introducing test cases
> using the 9pfs 'local' filesystem driver:
>
> https://github.com/qemu/qemu/blob/master/tests/qtest/virtio-9p-test.c
>
> So the idea was to resolve that chicken egg problem of this issue that way and
> also handle it a bit more systematically. If you now run qemu's 9p tests with
> latest git version (or at least with yesterday's QEMU 5.2 rc1 tarball):
>
> cd qemu/build
> make
> export QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64
> tests/qtest/qos-test
>
> these tests will now create a test directory qtest-9p-local-XXXXXX under the
> current directory (i.e. the build directory) where they are creating real
> directories and files like on a production system would do, just without a
> guest OS.
>
> As you can see, there are already 9p tests for creating and deleting
> directories, files, symlinks and hard links, etc.
>
> Maybe somebody interested to see this issue resolved in qemu might help by
> rebasing Greg's old patches and testing it with some test cases this way.
> Personally I need to work on some other things in the next couple weeks, but
> if somebody needs help, questions, review, etc., I'll be there.
Great news, nice work there.
I see the new tests it doesn't look hard to add new ones reproducing
open-unlink-fstat for example; I think it's good to have regardless of
kernel progress.
We'll get there!
--
Dominique
next prev parent reply other threads:[~2020-11-04 11:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 14:11 [PATCH RFC v2 0/4] 9p: fix open-unlink-f*syscall bug Jianyong Wu
2020-09-23 14:11 ` [PATCH v2 1/4] fs/9p: fix create-unlink-getattr idiom Jianyong Wu
2020-09-23 14:11 ` [PATCH v2 2/4] fs/9p: track open fids Jianyong Wu
2020-09-23 14:11 ` [PATCH v2 3/4] fs/9p: search open fids first Jianyong Wu
2020-09-23 14:11 ` [PATCH RFC v2 4/4] 9p: fix race issue in fid contention Jianyong Wu
2020-09-23 14:49 ` Dominique Martinet
2020-09-24 8:38 ` Jianyong Wu
2020-09-24 8:56 ` Greg Kurz
2020-09-24 9:51 ` Dominique Martinet
2020-09-25 9:49 ` Jianyong Wu
2020-11-03 10:41 ` Dominique Martinet
2020-11-04 11:32 ` Christian Schoenebeck
2020-11-04 11:57 ` Dominique Martinet [this message]
2020-11-05 12:32 ` Christian Schoenebeck
2020-11-05 7:05 ` Jianyong Wu
2020-11-19 16:06 ` [PATCH 0/2] follow-up to " Dominique Martinet
2020-11-19 16:06 ` [PATCH 1/2] 9p: apply review requests for fid refcounting Dominique Martinet
2020-11-19 16:06 ` [PATCH 2/2] 9p: Fix writeback fid incorrectly being attached to dentry Dominique Martinet
-- strict thread matches above, loose matches on Subject: below --
2020-09-24 4:50 [PATCH RFC v2 4/4] 9p: fix race issue in fid contention kernel test robot
2020-09-24 7:01 ` Dan Carpenter
2020-09-24 8:29 [kbuild] " Reshetova, Elena
2020-09-24 8:40 ` Dan Carpenter
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=20201104115708.GA30104@nautica \
--to=asmadeus@codewreck.org \
--cc=ericvh@gmail.com \
--cc=groug@kaod.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.