From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org,
"Antonios Motakis" <antonios.motakis@huawei.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 0/3] 9p: Fix file ID collisions
Date: Fri, 13 Sep 2019 19:01:57 +0200 [thread overview]
Message-ID: <20190913190157.651fc3a6@bahia.lan> (raw)
In-Reply-To: <cover.1567680121.git.qemu_oss@crudebyte.com>
On Thu, 5 Sep 2019 12:42:01 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
> This is v7 of a proposed patch set for fixing file ID collisions with 9pfs.
>
So I did some changes in 1/3 and pushed everything to 9p-next. I'll do some
more manual testing and issue a PR when I'm confident enough.
It would be nice to have some sort of automated test for that in 'make check'.
My first thought is to simulate a cross-device setup with the synth backend,
because it might be difficult to do this on a real filesystem without requiring
elevated privileges.
> v6->v7:
>
> * Rebased to https://github.com/gkurz/qemu/commits/9p-next
> (SHA1 7fc4c49e91).
>
> * Be pedantic and abort with error on wrong value for new command line
> argument 'multidevs'.
>
> * Adjusted patches to qemu code style guidelines.
>
> * Fixed potential crash in qp_table_destroy() on error path.
>
> * Use dedicated hash table init functions (qpd_table_init(),
> qpf_table_init(), qpp_table_init()):
> https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg00144.html
>
> * Use warn_report_once() instead of error_report_once() for issues
> interpreted merely as being warnings, not errors.
>
> * Simplified hash table destruction (due to simplified error path
> introduced by SHA1 7fc4c49e91).
>
> * Dropped capturing root_ino for now:
> https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg00146.html
>
> * Don't update proxy docs, since new command line argument 'multidevs' is
> limited to the local backend for now.
>
> * Mention in docs that readdir() is currently not blocked by
> 'multidevs=forbid'.
>
> * Rename qid_path_prefixmap() -> qid_path_suffixmap() in patch 3
> (due to the semantic change of that function by that patch).
>
> Christian Schoenebeck (3):
> 9p: Added virtfs option 'multidevs=remap|forbid|warn'
> 9p: stat_to_qid: implement slow path
> 9p: Use variable length suffixes for inode remapping
>
> fsdev/file-op-9p.h | 5 +
> fsdev/qemu-fsdev-opts.c | 7 +-
> fsdev/qemu-fsdev.c | 17 ++
> hw/9pfs/9p.c | 456 ++++++++++++++++++++++++++++++++++++++--
> hw/9pfs/9p.h | 59 ++++++
> qemu-options.hx | 26 ++-
> vl.c | 7 +-
> 7 files changed, 552 insertions(+), 25 deletions(-)
>
next prev parent reply other threads:[~2019-09-13 17:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 10:42 [Qemu-devel] [PATCH v7 0/3] 9p: Fix file ID collisions Christian Schoenebeck via Qemu-devel
2019-09-04 21:34 ` [Qemu-devel] [PATCH v7 1/3] 9p: Added virtfs option 'multidevs=remap|forbid|warn' Christian Schoenebeck via Qemu-devel
2019-09-04 22:05 ` [Qemu-devel] [PATCH v7 2/3] 9p: stat_to_qid: implement slow path Christian Schoenebeck via Qemu-devel
2019-09-04 22:53 ` [Qemu-devel] [PATCH v7 3/3] 9p: Use variable length suffixes for inode remapping Christian Schoenebeck via Qemu-devel
2019-09-13 17:01 ` Greg Kurz [this message]
2019-09-23 9:50 ` [Qemu-devel] [PATCH v7 0/3] 9p: Fix file ID collisions Christian Schoenebeck via
2019-09-23 12:56 ` Greg Kurz
2019-09-23 14:06 ` Christian Schoenebeck via
2019-09-23 14:46 ` Greg Kurz
2019-09-23 15:03 ` Christian Schoenebeck via
2019-09-23 16:50 ` Greg Kurz
2019-09-24 9:31 ` Christian Schoenebeck via
2019-10-08 9:14 ` Greg Kurz
2019-10-08 12:05 ` Christian Schoenebeck
2019-10-08 13:47 ` Greg Kurz
2019-10-08 14:25 ` Christian Schoenebeck
2019-10-08 14:45 ` Greg Kurz
2019-10-15 9:20 ` Greg Kurz
2019-10-16 9:42 ` virtio-fs: Fix file ID collisions (was: 9p: Fix file ID collisions) Christian Schoenebeck
2019-10-16 13:44 ` Dr. David Alan Gilbert
2019-10-18 13:15 ` Christian Schoenebeck
2019-10-16 14:00 ` Greg Kurz
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=20190913190157.651fc3a6@bahia.lan \
--to=groug@kaod.org \
--cc=antonios.motakis@huawei.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=stefanha@gmail.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).