[v2,0/4] 9p: Fix file ID collisions

Message

Zhijian Li (Fujitsu)" via May 3, 2019, 4:20 p.m. UTC

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(-)

Comments

Greg Kurz May 7, 2019, 9:28 a.m. UTC | #1

On Fri, 03 May 2019 18:20:39 +0200
Christian Schoenebeck <[e-mail]> 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: <[e-mail]>

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

Cheers,

--
Greg