Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp319819pxj; Tue, 18 May 2021 04:16:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwUQx567ROR6uH9L8/oyXrmbUsrl3hCKPhNqoUr8NpR3xKCV2utrkWONedODaYcK/cmx5iE X-Received: by 2002:a02:cbad:: with SMTP id v13mr5112040jap.86.1621336589294; Tue, 18 May 2021 04:16:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621336589; cv=none; d=google.com; s=arc-20160816; b=cJbspiaBpwJEP5TG5iyCUpApHJXVV/IbFzoAd7IWwj07/qte3CfeehEuxM/UaarW8D txCMg8rE4Lfa4o+wwS+Z3tPpL2B4GoE7pEuFahByVQ89edxl7E5WpnhNf+qJGdJAmiSM ak2wTonLhjKeCk2FfkzsgIBYEbnUwD9jWuN6n88pLRWEeF+vTn7um1A1pCZd/3w62ByS iI3L1oCOTF9NLvRLMG6CSquij8zAio0gJx9i/gvLsJ3DBTMBXkC5Z35dn568wgkBLE/G D5/LZtT3Znr4oymGvZHipwVEzCyHMYuzMtc4VVB4a3SuRjfHrC9kqAJCXj5GStdHbqhQ BDZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=wP0qVRRFLaqKdNsvIebHqzMAQA0sHv3p78V+XQan4IE=; b=obYuEcUzMzUsdxgOjtWWEZVAz0u+hRiJuuD/46D6pqe/eiOaUUkQnnaKwSbxpnDbtH 1Z0u6v1hvl4rT7y+dK5rGhjPsPjZ4Qx1N1DIKpxN+J5Cdi18WSzarGajT3lk0dZ2gi57 oOuxg4qcvLDfR+DLU2DLu7P/+F0AGVvzKBfZqmDn9gCvTnbbKEx4V+Ubeb8Wtj9DyduK 8qkhsp++oGzc/R29Vu6wWVfU4uDQ3iKxmT+u7Rw7hNzU+PlSOE6JEer1TgBRPOlURN2f s8xDOZOJkfekyqzzLY64b+aEMNKYMb/AvOmWMSRLfQyQ+EU6NEl02QhgiIsSbq9HyY3Y fk9g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=SIIetbEY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f6si21607625ioh.32.2021.05.18.04.16.16; Tue, 18 May 2021 04:16:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=SIIetbEY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242964AbhEQPR3 (ORCPT + 99 others); Mon, 17 May 2021 11:17:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48686 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241351AbhEQPG6 (ORCPT ); Mon, 17 May 2021 11:06:58 -0400 Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ACF2DC08EAE9; Mon, 17 May 2021 07:24:22 -0700 (PDT) Received: by mail-ot1-x330.google.com with SMTP id u19-20020a0568302493b02902d61b0d29adso5670713ots.10; Mon, 17 May 2021 07:24:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=wP0qVRRFLaqKdNsvIebHqzMAQA0sHv3p78V+XQan4IE=; b=SIIetbEYExbcUM1QfmpytUTa2IVHHxjrX5L6JO2j1xRF6GNf1rzKAyM40K3Hi5hYwf REzXM3GmnmYKtfOC3JTzd+8Q5wzYuan+AmqRuwrgoXOPPqC9S/ccK8CLcBCIZT7ro76q vdQ4N0tLO/zXJP4b5wg1VMck/JcqcLbL+m0YijN1z9Wy4KH1jVjVXeFNlbqjhBuEZpFL clyJPWEn6AwkURWyVxA9BsFa3GCFHCy/9/3s1au+ksMHEydPpvbnXHqdH34qXED252Fr 3ipPzVpKQiT02tYGuDwi4Puho9+BjNndIhyvsV44R5iSoKNE4kJ2qajjZsijf8TctP+u qB3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=wP0qVRRFLaqKdNsvIebHqzMAQA0sHv3p78V+XQan4IE=; b=osMoT7u9T5fXUzO5HXAqTH1oLoA5zd5l+57LBKYBRAZOZY5Ph3o4owJ/0b/DQMa/zo J9cxcUmHpxFLryZEnhKC1elFv9BOcHOmAtoXI/7Trj54YSGtFdMnOfIsi6CBy5JJIHeo iIZEQCvxv2lLclDr9+siCCpmakBN6lVU6jWv67oqDHw7cESaGJEnNSDp5bbpvYWCH+N7 duojR+cZN2zqlf2QBvueN5gzxxu5J6m0U5J9748S4ziAe/f4NWovf9/kuYXLBIRhNTl9 5iYAhF5vo7PM2yBTWBEe1Vo38S9tgC/I8wYWC86gVyxeaNamolO/rgBw0/OdT7F/NpCY PH0w== X-Gm-Message-State: AOAM533YJjx3Z8vU1/EKkOIuWoLCUx/2pxDNGvlyv8qt/FJqSMwtug0s q3aXOOMVgYxHHUCv3BJK9zY= X-Received: by 2002:a9d:4e88:: with SMTP id v8mr28025140otk.110.1621261462130; Mon, 17 May 2021 07:24:22 -0700 (PDT) Received: from [192.168.99.80] (142-79-211-230.starry-inc.net. [142.79.211.230]) by smtp.gmail.com with ESMTPSA id 19sm2728380oiy.11.2021.05.17.07.24.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 May 2021 07:24:21 -0700 (PDT) Subject: Re: [PATCH v2 1/4] usb: early: Avoid using DbC if already enabled To: Jan Beulich Cc: Jann Horn , Lee Jones , Chunfeng Yun , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org, Greg Kroah-Hartman References: <8ccce25a-e3ca-cb30-f6a3-f9243a85a49b@suse.com> <16400ee4-4406-8b26-10c0-a423b2b1fed0@gmail.com> From: Connor Davis Message-ID: <55325db1-b086-fc81-9117-6560c4914a12@gmail.com> Date: Mon, 17 May 2021 08:24:41 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/17/21 8:13 AM, Jan Beulich wrote: > On 17.05.2021 15:48, Connor Davis wrote: >> On 5/17/21 3:32 AM, Jan Beulich wrote: >>> On 14.05.2021 02:56, Connor Davis wrote: >>>> Check if the debug capability is enabled in early_xdbc_parse_parameter, >>>> and if it is, return with an error. This avoids collisions with whatever >>>> enabled the DbC prior to linux starting. >>> Doesn't this go too far and prevent use even if firmware (perhaps >>> mistakenly) left it enabled? >> Yes, but how is one supposed to distinguish the broken firmware and >> non-broken >> >> firmware cases? > Well, a first step might be to only check if running virtualized. > And then if your running virtualized, there might be a way to > inquire the hypervisor? Right, but if it was enabled by something other than a hypervisor, or you're not running virtualized, how do you distinguish then? IMO the proper thing to do in any case is to simply not use the DbC in linux. Thanks, Connor