Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3196132imm; Mon, 10 Sep 2018 12:37:04 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYAESgLkf3urljfWHib+IxMpe1sBlOFtASAZvTeAx6dNJq9rms/lg/vufb6YkcT6m1abAxw X-Received: by 2002:a63:ee15:: with SMTP id e21-v6mr24492537pgi.421.1536608224090; Mon, 10 Sep 2018 12:37:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536608224; cv=none; d=google.com; s=arc-20160816; b=Cyo62DtwCwfBmZdR/mNSDndWCzGssWs+FPplJPi80Tgz/vbSBeMCYuCXq1rXpxGGCh jdeU5tRDXF33CN7Db2MF43nhY06VIutfjN1azWZbz6dpY4b0nd2w1k7HAdIwPmBJSQZe hPI+pj8TPrMFe2+pL5dQ874hpXSgjschp3GZjaUnlgYUF4frbNGBcxKxrXpAEvh7/85S pILSI2mxS5kRZ4OFFKgJ3Ek/GTNijnvV/hpt+5ePqpcQ9P1vh/hB2LPmeEJrPUY/m04+ 2VUbuGm6rAkoC15NHPjL/0hmHFMS3Av0v5LAyoMcnzwVunWF+lSVxekwTcZVXecvmpxS Sjjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=N/++QHVpJujboPaI174+OFydt4Cyaq5Tf+pScJrPNho=; b=z8bQv1kFC9irp0rk7yiHgr7tjbhPeFkz+Gc4ADpyynmKUcAASpSjsb1sKKHrwufQhF ezyMlTUVuqiAwROHSwejnScc3sgT4KMa/xTgdnl+Ip9DUD6N1W6JX1h033ZOakITYNpH bPvDW7OcHMEsIQlCbEA6T079d44FWwqZeZEGYXqYy9/OHMSQNRkAfo+pssDJ/Q2qm1pH 0ABEGDDHciZ2OC3HntEHoYKNXXd70CUtyoDHMg8jHzJFZbgFQC5VYtKZ8w4Hjq/cH0Aa dYjmEZII+q4sArTPCJZHIyKnvlcb92mi73CT8oT+ic7g01AQ42zBBSUnU/nOcHpZ0S0Q HUFQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a1-v6si18153663pli.472.2018.09.10.12.36.48; Mon, 10 Sep 2018 12:37:04 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728347AbeIKAbw (ORCPT + 99 others); Mon, 10 Sep 2018 20:31:52 -0400 Received: from mx2.suse.de ([195.135.220.15]:40836 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727742AbeIKAbw (ORCPT ); Mon, 10 Sep 2018 20:31:52 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 12CCEAF8B; Mon, 10 Sep 2018 19:36:14 +0000 (UTC) Date: Mon, 10 Sep 2018 21:36:12 +0200 (CEST) From: Jiri Kosina To: "Schaufler, Casey" cc: Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Josh Poimboeuf , Andrea Arcangeli , "Woodhouse, David" , Andi Kleen , Tim Chen , "linux-kernel@vger.kernel.org" , "x86@kernel.org" Subject: RE: [PATCH v5 1/2] x86/speculation: apply IBPB more strictly to avoid cross-process data leak In-Reply-To: <99FC4B6EFCEFD44486C35F4C281DC6732144AEC9@ORSMSX107.amr.corp.intel.com> Message-ID: References: <99FC4B6EFCEFD44486C35F4C281DC6732144ADF9@ORSMSX107.amr.corp.intel.com> <99FC4B6EFCEFD44486C35F4C281DC6732144AEC9@ORSMSX107.amr.corp.intel.com> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 10 Sep 2018, Schaufler, Casey wrote: > Yes, It would require that this patch be tested against all the existing > security modules that provide a ptrace_access_check hook. It's not like > the security module writers don't have a bunch of locking issues to deal > with. Yeah, that was indeed my concern. So can we agree on doing this in the 2nd envisioned step, when this is going to be replaced by LSM as discussed [1] previously? [1] http://lkml.kernel.org/r/99FC4B6EFCEFD44486C35F4C281DC67321447094@ORSMSX107.amr.corp.intel.com Thanks, -- Jiri Kosina SUSE Labs