qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org, Antonios Motakis <antonios.motakis@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] 9p: Fix file ID collisions
Date: Tue, 7 May 2019 11:28:04 +0200	[thread overview]
Message-ID: <20190507112804.23cde966@bahia.lan> (raw)
In-Reply-To: <1926077.q6xKvCkoZ9@silver>

On Fri, 03 May 2019 18:20:39 +0200
Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:

> Hi!
> 
> This is v2 of a proposed patch set for fixing file ID collisions with 9pfs.
> 
> Patch 1 to 3 are identical to the previous version. New in this v2 is patch 4
> which introduces variable length suffixes for inode mapping instead of fixed
> length prefixes.
> 
> Also: patch 4 disables file ID persistency at compile time by default for now,
> since I am yet unresolved about details of that persistency.
> 
> Christian Schoenebeck (4):
>   9p: mitigates most QID path collisions
>   9P: trivial cleanup of QID path collision mitigation
>   9p: persistency of QID path beyond reboots / suspensions
>   9p: use variable length suffixes for inode mapping
> 
>  fsdev/9p-marshal.h   |    6 +-
>  hw/9pfs/9p.c         | 1145 ++++++++++++++++++++++++++++++++++++++++++++++++--
>  hw/9pfs/9p.h         |  167 ++++++++
>  hw/9pfs/trace-events |   14 +-
>  4 files changed, 1296 insertions(+), 36 deletions(-)
> 

Hmm... this series comes unthreaded again because the cover has:

Message-ID: <1926077.q6xKvCkoZ9@silver>

while the patches have:

In-Reply-To: <cover.1556896526.git.qemu_oss@crudebyte.com>

Maybe consider using git send-email or stgit mail to have proper
threading for free.

Cheers,

--
Greg


      parent reply	other threads:[~2019-05-07  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 16:20 [Qemu-devel] [PATCH v2 0/4] 9p: Fix file ID collisions Christian Schoenebeck
2019-05-03 16:20 ` Christian Schoenebeck via Qemu-devel
2019-05-07  9:28 ` Greg Kurz [this message]

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=20190507112804.23cde966@bahia.lan \
    --to=groug@kaod.org \
    --cc=antonios.motakis@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu_oss@crudebyte.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).