Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp6068887ybi; Wed, 29 May 2019 02:19:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqxRCUI5eT9g7mTUl36zl8Y6hccN4CbPIG3tZByJUpF+xCD6Bnq58YorKnKeZMCpU2A/cRdl X-Received: by 2002:a17:902:a5c5:: with SMTP id t5mr20369840plq.288.1559121558880; Wed, 29 May 2019 02:19:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559121558; cv=none; d=google.com; s=arc-20160816; b=alnlNbnD+ly0H3oW/hMvniXTFBLmLSST6ZXRmLgeP8FRSwjZ1fmleYyh9RhuFn3kcP qIkPxXbRMhNqQnUWVAD8OlLCizKPnXVmHXzwWg2Js3UeRJ0cj8QN0Qk8nnXWwyKqsisW X5RHT0Lhn1RVqc/KiUsLUddyn18XJ0JGKdf9XQrDcWNk7cMQ9w0gf0jXRLWT6Oj+3iCy nDdIu7n/olJFkUdlDxhaaXQbWE2exrfwY6q4iseC+1GZzqQflD5aUGPYjF7dTgwopSrR EkcddMiAfZ+N7dNlCX+qAJBAITYLx9eyFfsP1zQhPUVMZgTEvJ7it3nR/Vwfqj+81eyC SU+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=IO8RCdLJsonso++8E0RquH3KfBxivFE8uJzUXXpSO44=; b=fZBB6gyQe5PU/GchqNSOhRRqsCd21RpNDvAiqcIuM0vWo+YMdD9HlxkM1svRZUMBZD zIeTsv/BBXcea0PBUKvBFrdtledV+CDFRIuSbIK4NIPYRMLjQXBKswULqoOEMULICsm3 nRcbIxnW2uKD0zBDUHWnjFuayx9gZgG3gZA2v37csJredQNbS1Twhbe4xjEywkXaLjla ZgqNOek8sVFav6JDaZHYQlMJD6mlUz4mTDVCzgf8Tt1+qFM2hmervkICgCoNKWL6gJ+7 sVScEiNosZPbmuDGSYAycEPwyqoWioSMdSUTY/Hju5Mchl9kl5EeY9VY/Eyu2eJhbNs3 sb6Q== 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 d34si22934310pgd.558.2019.05.29.02.19.01; Wed, 29 May 2019 02:19:18 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726231AbfE2JRn (ORCPT + 99 others); Wed, 29 May 2019 05:17:43 -0400 Received: from foss.arm.com ([217.140.101.70]:41640 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725861AbfE2JRn (ORCPT ); Wed, 29 May 2019 05:17:43 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 05C1F341; Wed, 29 May 2019 02:17:43 -0700 (PDT) Received: from fuggles.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C177F3F5AF; Wed, 29 May 2019 02:17:40 -0700 (PDT) Date: Wed, 29 May 2019 10:17:33 +0100 From: Will Deacon To: Peter Zijlstra Cc: Young Xiao <92siuyang@gmail.com>, linux@armlinux.org.uk, mark.rutland@arm.com, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org, kan.liang@linux.intel.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, ravi.bangoria@linux.vnet.ibm.com, mpe@ellerman.id.au Subject: Re: [PATCH] perf: Fix oops when kthread execs user process Message-ID: <20190529091733.GA4485@fuggles.cambridge.arm.com> References: <1559046689-24091-1-git-send-email-92siuyang@gmail.com> <20190528140103.GT2623@hirez.programming.kicks-ass.net> <20190528153224.GE20758@fuggles.cambridge.arm.com> <20190528173228.GW2623@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190528173228.GW2623@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.11.1+86 (6f28e57d73f2) () Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 28, 2019 at 07:32:28PM +0200, Peter Zijlstra wrote: > On Tue, May 28, 2019 at 04:32:24PM +0100, Will Deacon wrote: > > On Tue, May 28, 2019 at 04:01:03PM +0200, Peter Zijlstra wrote: > > > On Tue, May 28, 2019 at 08:31:29PM +0800, Young Xiao wrote: > > > > When a kthread calls call_usermodehelper() the steps are: > > > > 1. allocate current->mm > > > > 2. load_elf_binary() > > > > 3. populate current->thread.regs > > > > > > > > While doing this, interrupts are not disabled. If there is a perf > > > > interrupt in the middle of this process (i.e. step 1 has completed > > > > but not yet reached to step 3) and if perf tries to read userspace > > > > regs, kernel oops. > > > > This seems to be because pt_regs(current) gives NULL for kthreads on Power. > > 'funny' thing that, perf_sample_regs_user() seems to assume that > anything with current->mm is in fact a user task, and that assumption is > just plain wrong, consider use_mm(). Right, I suppose that was attempting to handle interrupt skid from the PMU overflow? > So I'm thinking the right thing to do here is something like the below; > umh should get PF_KTHREAD cleared when it passes exec(). And this should > also fix the power splat I'm thinking. > > --- > > diff --git a/kernel/events/core.c b/kernel/events/core.c > index abbd4b3b96c2..9929404b6eb9 100644 > --- a/kernel/events/core.c > +++ b/kernel/events/core.c > @@ -5923,7 +5923,7 @@ static void perf_sample_regs_user(struct perf_regs *regs_user, > if (user_mode(regs)) { > regs_user->abi = perf_reg_abi(current); > regs_user->regs = regs; > - } else if (current->mm) { > + } else if (!(current->flags & PF_KTHREAD) && current->mm) { > perf_get_regs_user(regs_user, regs, regs_user_copy); Makes sense, but under which circumstances would we have a NULL mm here? Will