Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2979715imu; Sun, 9 Dec 2018 14:11:00 -0800 (PST) X-Google-Smtp-Source: AFSGD/Wty1nG7UqQhXklMhUUuNTxZH8ZB7sj9PEwzTF4lpG2rOmghpfBmDxllD5RqPKKaav+rNXI X-Received: by 2002:a63:c70d:: with SMTP id n13mr9016642pgg.108.1544393460932; Sun, 09 Dec 2018 14:11:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544393460; cv=none; d=google.com; s=arc-20160816; b=RVqtIYgB2JJpAbUZhcMu8CcHV/VmlCUHYSctOVLUTbMA9rdnjApNE9VGrCiEc/kTWq opXtGdzXriNPfkfFD0s8w/vYZzA0kj1UdnwyqRzyeCS81pm6LkWQ17KKAol8uQtqrGJL tOIq5Cxe0LfdCI3XPv7j6ooiRwLtazg0SeSuqyVnw13PqvK+WoxVDKRpwFExGmcoDCix fw7Y6kPe7mAlf6zXqFg1VUnGw+RrRnABEzeoo+HKFZ3ijFk03jkmZznUjUuxNeWuMjGw EfVw3cu4z1ZMnuPKS0JM7hQjJdlzzQEZ9r7FExb4uRI7K1+UohbSwJt717p8h7cV2MRL RNTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=aZIHol3LwmqMbokKuKhRspjc5AyT3UueeW6ak/rASkQ=; b=apy7rRWtVQiFhzRjRuVG0zCU5bEFsio05qmdgfRwWrBLlp0lGx6LqZngweCtRP1TZD JiQZcSU2jhXf/HoIcb+a2eUTAfds4QNH41PlYS1Sa8pW2sJpbqDHnqk/HblO3gnWW2Qw 6kZRIPlUorDSsh9NnPi7PU+nssLwO4l797Z5vyqLIRZlSGmCw0tfT7az/cNc8q70nkSs ENvF15dOqTAGa5PJ8bWlqiyZ1I0rglmKCbjzdEQhtjhddHt1syieb9XeEOoL4DX9jjGv 3eY4J8evn8Fc8FVcftvP5hCbjm0ILB7i/bS142+eFGlU2utRqwz5pH49/5P8FYd3Pdjy cJ3w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j24si8414099pgn.149.2018.12.09.14.10.46; Sun, 09 Dec 2018 14:11:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728093AbeLIWJW (ORCPT + 99 others); Sun, 9 Dec 2018 17:09:22 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:37422 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727045AbeLIWJS (ORCPT ); Sun, 9 Dec 2018 17:09:18 -0500 Received: from pub.yeoldevic.com ([81.174.156.145] helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gW73F-0002pp-Li; Sun, 09 Dec 2018 21:55:49 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gW72d-0003NT-49; Sun, 09 Dec 2018 21:55:11 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Dominique Martinet" , "Chirantan Ekbote" , "Dylan Reid" , "Guenter Roeck" , "Greg Kurz" Date: Sun, 09 Dec 2018 21:50:33 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 128/328] 9p/net: Fix zero-copy path in the 9p virtio transport In-Reply-To: X-SA-Exim-Connect-IP: 81.174.156.145 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.62-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Chirantan Ekbote commit d28c756caee6e414d9ba367d0b92da24145af2a8 upstream. The zero-copy optimization when reading or writing large chunks of data is quite useful. However, the 9p messages created through the zero-copy write path have an incorrect message size: it should be the size of the header + size of the data being written but instead it's just the size of the header. This only works if the server ignores the size field of the message and otherwise breaks the framing of the protocol. Fix this by re-writing the message size field with the correct value. Tested by running `dd if=/dev/zero of=out bs=4k count=1` inside a virtio-9p mount. Link: http://lkml.kernel.org/r/20180717003529.114368-1-chirantan@chromium.org Signed-off-by: Chirantan Ekbote Reviewed-by: Greg Kurz Tested-by: Greg Kurz Cc: Dylan Reid Cc: Guenter Roeck Signed-off-by: Dominique Martinet [bwh: Backported to 3.16: adjust context] Signed-off-by: Ben Hutchings --- net/9p/trans_virtio.c | 7 +++++++ 1 file changed, 7 insertions(+) --- a/net/9p/trans_virtio.c +++ b/net/9p/trans_virtio.c @@ -378,6 +378,7 @@ p9_virtio_zc_request(struct p9_client *c p9_debug(P9_DEBUG_TRANS, "virtio request\n"); if (uodata) { + __le32 sz; out_nr_pages = p9_nr_pages(uodata, outlen); out_pages = kmalloc(sizeof(struct page *) * out_nr_pages, GFP_NOFS); @@ -393,6 +394,12 @@ p9_virtio_zc_request(struct p9_client *c out_pages = NULL; goto err_out; } + /* The size field of the message must include the length of the + * header and the length of the data. We didn't actually know + * the length of the data until this point so add it in now. + */ + sz = cpu_to_le32(req->tc->size + outlen); + memcpy(&req->tc->sdata[0], &sz, sizeof(sz)); } if (uidata) { in_nr_pages = p9_nr_pages(uidata, inlen);