Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2982498pxb; Tue, 21 Sep 2021 11:43:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw0QTD1M45mtgIENDdpzU/fSM10m9+gv3eOe2/XBnrnelb/aiflcU4hmB3MlZi5yrONQKIb X-Received: by 2002:aa7:c38c:: with SMTP id k12mr37381989edq.45.1632249813963; Tue, 21 Sep 2021 11:43:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632249813; cv=none; d=google.com; s=arc-20160816; b=p21konrka4mcAKjI2FP6vmdKDbhau0Yrwu0yA03pmWDgw/2td39v7DLt1m3AwLWvB2 4D/V3gE6FKajkiiAxUCDRfanobnrUjDdG6Nb8N3K6A1UTmQy+/ya6ZSBZltzSjovRj3B jQUYwpIZtrlqKNtoUw5li/B0+G/ZzxTcF+zPtCkgsX9p3rrxVd4ALgin4wRKS34TCrcz XKqTK2J/gBypW59wYEtI48Gsf/q0PXgPYd5tA51FsHDdQJ4bL3fb2PUehP4pK0V0QT5P Tv9Am7ZtsJk8V2SuwXTNpJJTbW4+9DalzpK4v2e+khM9riQPltpQgymPWgi7NlIOER0p 3HSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:content-disposition :content-transfer-encoding:mime-version:in-reply-to:references:cc :user-agent:date:subject:to:from; bh=jSQznwMeV7UkDjrdgTC7N3dACQhLNXd8ojDszAeGGjA=; b=oi+7Q5GUPDkoO8KbcTdyu/iUrdMXN3TXqv/fiTGh4sSuo8SXBM3vRPRXKLVuVKoXa7 DWc9F30I/zOvoQZSGhVMxulCGqYwarTlLaf58T9YFByjn0JxHFD8PohhHHefg+yyvC6Q QLFkiZU+1f0ZM2uGVxQ0C/b2UST4IHIZrzEJrMUHdIIOKaqDiluNBTHFOy83E20OMXQn L0kkgm0J5fix/RmGb515x4vcFvN7E8Cs5BNXLYVmNG0tjnUObOoG6N6Ma8C4PBqMo9JU O8ti+Klx9dCEMIG2108FmD7dUDyrnccmsYeJgp1TdFEhOXdnL+hSGKIZ1D6lnkrpoYv1 9V5Q== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t14si21798994ejy.51.2021.09.21.11.43.09; Tue, 21 Sep 2021 11:43:33 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231532AbhIURgM (ORCPT + 99 others); Tue, 21 Sep 2021 13:36:12 -0400 Received: from hosting.gsystem.sk ([212.5.213.30]:43636 "EHLO hosting.gsystem.sk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231283AbhIURdK (ORCPT ); Tue, 21 Sep 2021 13:33:10 -0400 Received: from [192.168.0.2] (chello089173232159.chello.sk [89.173.232.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hosting.gsystem.sk (Postfix) with ESMTPSA id 230C57A0212; Tue, 21 Sep 2021 19:31:40 +0200 (CEST) From: Ondrej Zary To: Peter Zijlstra Subject: Re: [tip: x86/core] x86/iopl: Fake iopl(3) CLI/STI usage Date: Tue, 21 Sep 2021 19:31:36 +0200 User-Agent: KMail/1.9.10 Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org, Thomas Gleixner , x86@kernel.org References: <20210918090641.GD5106@worktop.programming.kicks-ass.net> <202109211309.26518.linux@zary.sk> In-Reply-To: X-KMail-QuotePrefix: > MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <202109211931.37066.linux@zary.sk> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 21 September 2021 14:00:59 Peter Zijlstra wrote: > On Tue, Sep 21, 2021 at 01:09:26PM +0200, Ondrej Zary wrote: > > On Tuesday 21 September 2021, tip-bot2 for Peter Zijlstra wrote: > > > The following commit has been merged into the x86/core branch of tip: > > > > > > Commit-ID: 32e1ae626f295152d1fc9a3375214133cbe62878 > > > Gitweb: https://git.kernel.org/tip/32e1ae626f295152d1fc9a3375214133cbe62878 > > > Author: Peter Zijlstra > > > AuthorDate: Fri, 17 Sep 2021 11:20:04 +02:00 > > > Committer: Peter Zijlstra > > > CommitterDate: Sat, 18 Sep 2021 12:18:32 +02:00 > > > > > > x86/iopl: Fake iopl(3) CLI/STI usage > > > > > > Since commit c8137ace5638 ("x86/iopl: Restrict iopl() permission > > > scope") it's possible to emulate iopl(3) using ioperm(), except for > > > the CLI/STI usage. > > > > > > Userspace CLI/STI usage is very dubious (read broken), since any > > > exception taken during that window can lead to rescheduling anyway (or > > > worse). The IOPL(2) manpage even states that usage of CLI/STI is highly > > > discouraged and might even crash the system. > > > > > > Of course, that won't stop people and HP has the dubious honour of > > > being the first vendor to be found using this in their hp-health > > > package. > > > > > > In order to enable this 'software' to still 'work', have the #GP treat > > > the CLI/STI instructions as NOPs when iopl(3). Warn the user that > > > their program is doing dubious things. > > > > > > Fixes: a24ca9976843 ("x86/iopl: Remove legacy IOPL option") > > > Reported-by: Ondrej Zary > > > Signed-off-by: Peter Zijlstra (Intel) > > > Reviewed-by: Thomas Gleixner > > > Link: https://lkml.kernel.org/r/20210918090641.GD5106@worktop.programming.kicks-ass.net > > > > Could this be backported to 5.10 kernel so it can get into the recently released Debian 11? > > Thomas also asked about a stable tag, so I'll rebase and force-push > these commits and add: > > Cc: stable@kernel.org # v5.5+ > > to it. > Thank you very much for great work. -- Ondrej Zary