Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B3BEAC282CA for ; Wed, 13 Feb 2019 15:45:47 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 835D22190A for ; Wed, 13 Feb 2019 15:45:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ZVCmnRm4"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="pmf+EjiX" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 835D22190A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=EVjo3TlB55DLPb2hb94H9iFrvHUrsXKQtFCyKh9PyGo=; b=ZVCmnRm41HW3CL poZZYJKbz0vTVQF8+Vr6WXghMr9Mtyb1UP1FZqgwxh6cN/42Su911rAlj4PCPemARBbpHKaEyWN6a NzOxlrjyVlhD3epBnU1DlWQ3K1AT3CUR60ozRiRRuK2/azvVIQJSztSEFhxLKjEo5j5rRHUaRZ5Q1 n909c7tczBY/d2+BmWRy3IUoDHRzeb68F5HHfI1uzCXT/d2GJmrVc+IyVHy9elAGJ23NDnrpon3pl L7UZvGZpGYsnLrj/gIJ1FWC2151eYhE3bpISkuoyagz4eWMAVXFq4bmsfyEqS5NahfBQ7WsOs2fNf NrWxyYrUxwYidkOzthaQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gtwjF-0008PX-Cy; Wed, 13 Feb 2019 15:45:41 +0000 Received: from merlin.infradead.org ([2001:8b0:10b:1231::1]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gtwjE-0008PM-3u for linux-arm-kernel@bombadil.infradead.org; Wed, 13 Feb 2019 15:45:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HdDbBwL10xwWBHY4uWjVzdQtLeyqbXrybLGpZsQT0UM=; b=pmf+EjiXP0Q+miXdMnvJTukG+ SBVzKFzdcy1FkY2pE6D0dizvTy1+lE633fvRou2Meq7LfU72PE3pTBU5uFac4VjBhSO2L6R3jTE6e J0GUvZkAx7o59SnsquPcxZY2QgOWEI87xwt7zxgnWDRW+KqYoOiUwFjztTQBJZyfjbLUQQw4N1v3W stPt6jqH2O2hvEs3pkp0W+icxMvVAY8AFfCQ+VNksRf2uDfNHPP7O7DIAdgGLjm5Oufg76AQyfjqG 839j1yhEFn1AjpLaX/SHev5KJOTmwtA6/JGQoNYuQ2SFCSjEsFLtET3t/FC7SKVUL05UgkOGMFV9p 82zt5GZkQ==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1gtwj8-0002Gs-JV; Wed, 13 Feb 2019 15:45:34 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 2AFA1202CEF72; Wed, 13 Feb 2019 16:45:32 +0100 (CET) Date: Wed, 13 Feb 2019 16:45:32 +0100 From: Peter Zijlstra To: Julien Thierry Subject: Re: [PATCH v3 3/4] uaccess: Check no rescheduling function is called in unsafe region Message-ID: <20190213154532.GQ32534@hirez.programming.kicks-ass.net> References: <20190211134527.GA121589@gmail.com> <20190211135159.GC32511@hirez.programming.kicks-ass.net> <20190213103553.GO32494@hirez.programming.kicks-ass.net> <1c2429a4-9df9-40a3-98e0-51577de4bd6a@arm.com> <20190213131720.GU32494@hirez.programming.kicks-ass.net> <20190213140025.GB6346@brain-police> <20190213142524.GW32494@hirez.programming.kicks-ass.net> <20190213144145.GY32494@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190213144145.GY32494@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: dvlasenk@redhat.com, brgerst@gmail.com, catalin.marinas@arm.com, jpoimboe@redhat.com, Will Deacon , linux-kernel@vger.kernel.org, valentin.schneider@arm.com, mingo@redhat.com, james.morse@arm.com, luto@kernel.org, hpa@zytor.com, bp@alien8.de, tglx@linutronix.de, torvalds@linux-foundation.org, Ingo Molnar , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Feb 13, 2019 at 03:41:45PM +0100, Peter Zijlstra wrote: > On Wed, Feb 13, 2019 at 02:39:22PM +0000, Julien Thierry wrote: > > Hi Peter, > > > > On 13/02/2019 14:25, Peter Zijlstra wrote: > > > On Wed, Feb 13, 2019 at 02:00:26PM +0000, Will Deacon wrote: > > >> The difference is because getting preempted in the sequence above is > > >> triggered off the back of an interrupt. On arm64, and I think also on x86, > > >> the user access state (SMAP or PAN) is saved and restored across exceptions > > >> but not across context switch. > > > > > > A quick reading of the SDM seems to suggest the SMAP state is part of > > > EFLAGS, which is context switched just fine AFAIK. > > > > > I fail to see where this is happening when looking at the switch_to() > > logic in x86_64. > > Yeah, me too.. we obviously preserve EFLAGS for user context, but for > kernel-kernel switches we do not seem to preserve it :-( So I dug around the context switch code a little, and I think we lost it here: 0100301bfdf5 ("sched/x86: Rewrite the switch_to() code") Before that, x86_64 switch_to() read like (much simplified): asm volatile ( /* do RSP twiddle */ : /* output */ : /* input */ : "memory", "cc", .... "flags"); (see __EXTRA_CLOBBER) Which I suppose means that GCC generates the PUSHF/POPF to preserve the EFLAGS, since we mark those explicitly clobbered. Before that: f05e798ad4c0 ("Disintegrate asm/system.h for X86") We had explicit PUSHF / POPF in SAVE_CONTEXT / RESTORE_CONTEXT resp. Now I cannot see how the current code preserves EFLAGS (if indeed it does), and the changelog doesn't mention this change _AT_ALL_. For a little bit of context; it turns out that user_access_begin() / user_access_end() sets EFLAGS.AC and scheduling in between there wrecks that because we're apparently not saving that anymore. Now, I'm tempted to add the PUSHF / POPF right back because of this, but first I suppose we need to figure out if that change was on purpose and why that went missing from the Changelog. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel