Received: by 10.223.176.5 with SMTP id f5csp464090wra; Tue, 30 Jan 2018 14:28:14 -0800 (PST) X-Google-Smtp-Source: AH8x227ceMjYy9LFOabH4wzrtxp/k6S55ilUieKI2La0URpUw26RfETOOB7Ej/Vjm4t7ORLNfk++ X-Received: by 2002:a17:902:758b:: with SMTP id j11-v6mr5833261pll.224.1517351294126; Tue, 30 Jan 2018 14:28:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517351294; cv=none; d=google.com; s=arc-20160816; b=0ItNl5f18ny+PhMJWAAKh69O1bffyY1kwUTkV584ouqnT5bko4Ai8hZwBurn4kqyMh bY52x5qUynxyFfa7e33OUnSdeGkEpz9TuTtheH8ljs0AhQV5WBMDj1gMJkT9lvOjH83m +dghvQ983XFgYK3VdBFWDwqA0BmrdhnWcgH3wrG1iDBpMh7RSxpavSTkMq9GLyGLZ0oO t9r9q4pUoUrpprbyhHrccPskIbylKxHK98NfIOUshVPXvjh9lPsnMZ1w7CGaMArAydnG pSuWuzQJluozKwwAggtCkfHG4/xIkDJEiD45gLKYfEZnbRxfBWlUwgPaR0gGocd1BraA bteg== 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 :arc-authentication-results; bh=M20cgNCMgR2hn0PETdmwShxi90L15gyZ73JTddiLiDU=; b=xlGwE+MLYTN/WhTTqCB4Kn756boNWXYjL92DJqUlQV/MPYlOQZL0ExjGQuomOFFDM3 iLGb5QAHwrWxa9VhYx98fZPYYnd94uKkmPhA+LbrCdb0wTX1gLXAJ3rm8e2dWoTDd/De sTyEkuVM7dXwy8JhE2EM71pX2o5Cw/fZHal7C8LBkEwBT0hkR2pJZPi64xKuiYqcXNmk VMseBMbC2vsAuO9voPeZbOzCPg2p9to4YXkAZel6v3b8M38Kpe5dgNPm9zd8xANJEgD5 by4V6M6SzW95mygbEZTvwIGK3fOols8QTDNEBq0632Tq2lth2XAR+gk/s3w9falEKTOa bSZg== 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 y16-v6si1622694pll.82.2018.01.30.14.27.59; Tue, 30 Jan 2018 14:28:14 -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 S1752638AbeA3WWH (ORCPT + 99 others); Tue, 30 Jan 2018 17:22:07 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:45252 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752516AbeA3WWF (ORCPT ); Tue, 30 Jan 2018 17:22:05 -0500 Received: from p4fea5f09.dip0.t-ipconnect.de ([79.234.95.9] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1egeFA-00043K-S9; Tue, 30 Jan 2018 23:19:09 +0100 Date: Tue, 30 Jan 2018 23:21:58 +0100 (CET) From: Thomas Gleixner To: Borislav Petkov cc: Tim Chen , Josh Poimboeuf , David Woodhouse , arjan@linux.intel.com, karahmed@amazon.de, x86@kernel.org, linux-kernel@vger.kernel.org, peterz@infradead.org, pbonzini@redhat.com, ak@linux.intel.com, torvalds@linux-foundation.org, gregkh@linux-foundation.org, mingo@kernel.org, luto@kernel.org, linux@dominikbrodowski.net Subject: Re: [PATCH] x86/speculation: Use Indirect Branch Prediction Barrier in context switch In-Reply-To: <20180130220052.jotc4orxnzi6s3nx@pd.tnic> Message-ID: References: <1517263487-3708-1-git-send-email-dwmw@amazon.co.uk> <20180130174850.bwypk4r5yn2344jb@treble> <20180130220052.jotc4orxnzi6s3nx@pd.tnic> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 Jan 2018, Borislav Petkov wrote: > On Tue, Jan 30, 2018 at 01:23:17PM -0800, Tim Chen wrote: > > I'm less familiar with gpg-agent. Dave was the one who > > put in comments about gpg-agent in this patch so perhaps > > he can comment. > > So I looked at gpg-agent and AFAICT, it disables core dumping with > setrlimit(). setrlimit() does not end up fiddling with the dumpable bits in mm->flags. So no. > I wasn't able to attach to it either with gdb but didn't find where we > disable the attaching, for the couple of minutes I grepped through it. prctl(PR_SET_DUMPABLE, 0) = 0 That does the trick. Thanks, tglx