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=-4.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=no 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 34F41C49ED6 for ; Wed, 11 Sep 2019 13:03:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 11926206A1 for ; Wed, 11 Sep 2019 13:03:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726781AbfIKNDS (ORCPT ); Wed, 11 Sep 2019 09:03:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17050 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727659AbfIKNDR (ORCPT ); Wed, 11 Sep 2019 09:03:17 -0400 Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 88F355AFDE for ; Wed, 11 Sep 2019 13:03:17 +0000 (UTC) Received: by mail-qk1-f197.google.com with SMTP id 72so24823116qki.12 for ; Wed, 11 Sep 2019 06:03:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/sfNjqGMZWLcI3m0N4VrOWVEum1o031nknNQPF2WES8=; b=TWf6MJkgvn1PX0yRhhL0IVqqL1vaX2NNbCvMDpZKBy2Jx95q15/A9qb1L48bwTScwX vNnBu5w5StN9Ks0CjXiuraQ+UXVoBE5gyC53R92LQIJrnFTAW/JuAF5urQDZiQDM/OTo oIjtJeXNPzgUXql+MlYN4tUUxOUY0mvF4ad9BcWpu1lAmjPjnPqCqu6DVV8t+suWc7py +VRvc5CCHBRiw+prIDfmjNp9Nl0lDQ7w6iJoSI1iEscHqTY/zTAhveN6zOCKBtw87/0D gfrL4gmP7ke9E9cnkpsjZW7p7afkqEzbZ+iAYUngoZq+pdBNPVV0R+vL3Vgbe4XOXSGZ 4Itw== X-Gm-Message-State: APjAAAUH7zhrYrxlLTHeB+8vg9oN3/iPgey/eCBIE+J2sELjakAzWW99 WVK6R5OYnBqdg9QHwPnMgrqVdiks7e521wU3zoRQeSCfg08CPM8663YP9rLmR/6/3W2G+O+HB3k vY4rgP5elB2zyLopV X-Received: by 2002:ac8:7242:: with SMTP id l2mr35745600qtp.4.1568206996818; Wed, 11 Sep 2019 06:03:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqwmsmhjoHJTb7z6oORqOFoKPWxTBsyQouHREJ+8K5GPemL48MacSn+bJagBRzKL996ErgPJyA== X-Received: by 2002:ac8:7242:: with SMTP id l2mr35745571qtp.4.1568206996537; Wed, 11 Sep 2019 06:03:16 -0700 (PDT) Received: from redhat.com ([80.74.107.118]) by smtp.gmail.com with ESMTPSA id v2sm6615278qtv.22.2019.09.11.06.03.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Sep 2019 06:03:15 -0700 (PDT) Date: Wed, 11 Sep 2019 09:03:10 -0400 From: "Michael S. Tsirkin" To: Michal Hocko Cc: linux-kernel@vger.kernel.org, Jason Wang , kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org Subject: Re: [PATCH v2] vhost: block speculation of translated descriptors Message-ID: <20190911085807-mutt-send-email-mst@kernel.org> References: <20190911120908.28410-1-mst@redhat.com> <20190911121628.GT4023@dhcp22.suse.cz> <20190911082236-mutt-send-email-mst@kernel.org> <20190911123316.GX4023@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190911123316.GX4023@dhcp22.suse.cz> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Sep 11, 2019 at 02:33:16PM +0200, Michal Hocko wrote: > On Wed 11-09-19 08:25:03, Michael S. Tsirkin wrote: > > On Wed, Sep 11, 2019 at 02:16:28PM +0200, Michal Hocko wrote: > > > On Wed 11-09-19 08:10:00, Michael S. Tsirkin wrote: > > > > iovec addresses coming from vhost are assumed to be > > > > pre-validated, but in fact can be speculated to a value > > > > out of range. > > > > > > > > Userspace address are later validated with array_index_nospec so we can > > > > be sure kernel info does not leak through these addresses, but vhost > > > > must also not leak userspace info outside the allowed memory table to > > > > guests. > > > > > > > > Following the defence in depth principle, make sure > > > > the address is not validated out of node range. > > > > > > > > Signed-off-by: Michael S. Tsirkin > > > > Acked-by: Jason Wang > > > > Tested-by: Jason Wang > > > > > > no need to mark fo stable? Other spectre fixes tend to be backported > > > even when the security implications are not really clear. The risk > > > should be low and better to be covered in case. > > > > This is not really a fix - more a defence in depth thing, > > quite similar to e.g. commit b3bbfb3fb5d25776b8e3f361d2eedaabb0b496cd > > x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec > > in scope. > > > > That one doesn't seem to be tagged for stable. Was it queued > > there in practice? > > not marked for stable but it went in. At least to 4.4. So I guess the answer is I don't know. If you feel it's justified, then sure, feel free to forward. -- MST