From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:45306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMavV-0003Pq-UB for qemu-devel@nongnu.org; Fri, 03 May 2019 12:20:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMavU-000544-Lw for qemu-devel@nongnu.org; Fri, 03 May 2019 12:20:45 -0400 Received: from kylie.crudebyte.com ([5.189.157.229]:53547) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hMavU-0004zB-2V for qemu-devel@nongnu.org; Fri, 03 May 2019 12:20:44 -0400 From: Christian Schoenebeck Date: Fri, 03 May 2019 18:20:39 +0200 Message-ID: <1926077.q6xKvCkoZ9@silver> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [Qemu-devel] [PATCH v2 0/4] 9p: Fix file ID collisions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Greg Kurz , Antonios Motakis 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(-) -- 2.11.0 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87134C43219 for ; Fri, 3 May 2019 16:22:57 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 536DE20651 for ; Fri, 3 May 2019 16:22:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (4096-bit key) header.d=crudebyte.com header.i=@crudebyte.com header.b="YQtdHeyn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 536DE20651 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=nongnu.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([127.0.0.1]:43295 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMaxc-0004yl-JW for qemu-devel@archiver.kernel.org; Fri, 03 May 2019 12:22:56 -0400 Received: from eggs.gnu.org ([209.51.188.92]:45306) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMavV-0003Pq-UB for qemu-devel@nongnu.org; Fri, 03 May 2019 12:20:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMavU-000544-Lw for qemu-devel@nongnu.org; Fri, 03 May 2019 12:20:45 -0400 Received: from kylie.crudebyte.com ([5.189.157.229]:53547) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hMavU-0004zB-2V for qemu-devel@nongnu.org; Fri, 03 May 2019 12:20:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=crudebyte.com; s=kylie; h=Content-Type:Content-Transfer-Encoding: MIME-Version:Message-ID:Date:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=IjVkMgLXbokAhulZTvyt9DaCxjiGi1PgnfviFxDpTvk=; b=YQtdHeynogTv/YFLJ7xQYI9A2K 6oiIAFD/Rdk+CalACQfR8yET1u9D/k6HeO0bTZdofhKV8xIlZ5QLIBYpvzMRZYaT8RQPmg0+2KYwD 6FYyaFhlmaWjNTA2fw4TPVSo6LW2sJIWZ+OkusgY1lKwZ4IK3R7Jt+wgqH8WD5k+AUfx03fjFoTT/ 1ZzwLeuInTbPwmJbzmhKviXO92mhopdyxMW+TaHUdVRys7C85ZDadGZ4RRGrUJAZOrG3qoJArZVuG y23u1w152BwtcMf0Fvad8ClHpXemVTnKhjez1tBjBTqsHnfbUVm5kwpJTmelEct5PK3456QMPrXh5 NW0ij/ibOvXZPqNhrXV5GeDC42LId7PfQ5PJ22FrIv8CaSrAUiVhi4Zk+B58C8yGboNnkfU4jL5ww VRtv9FtXAoNYJ44X6xakpLfzd5IgQ7o/2OT9CamnN3kNDGdTCGbaMRQjJouWeTbN2d7PBv4h7YZkp 4pCsBr4V1KlQeY7xAVwt7SnsysVLlPGrGjQb4AeiJ2pp0rQ1sap4rK1/XLlSrnOiaOvs56w7YkKME TWRWHW+Eni1IZH6B/iLVNyn1AGVxYf/4dDZddRl9SUywZs1RQMKYx24Wd0ue1KYCclpCi3DULrQLj xVEj63qA/LUIWVIxfBcW1ElhDN4d3ghyYWYEpZsVU=; To: qemu-devel@nongnu.org Date: Fri, 03 May 2019 18:20:39 +0200 Message-ID: <1926077.q6xKvCkoZ9@silver> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-Spam_score: -0.0 X-Spam_score_int: 0 X-Spam_bar: / X-Spam_report: Spam detection software, running on the system "kylie.crudebyte.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: 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. Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 NO_RELAYS Informational: message was not relayed via SMTP -0.0 NO_RECEIVED Informational: message has no Received headers X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 5.189.157.229 Subject: [Qemu-devel] [PATCH v2 0/4] 9p: Fix file ID collisions X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Christian Schoenebeck via Qemu-devel Reply-To: Christian Schoenebeck Cc: Greg Kurz , Antonios Motakis Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" Message-ID: <20190503162039.pA382W29a-ZRYc1Qc3NYo_cUaZpcCRFVobN6egmHa84@z> 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(-) -- 2.11.0