Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp376742imm; Thu, 27 Sep 2018 23:25:12 -0700 (PDT) X-Google-Smtp-Source: ACcGV62Dd+RDDy8Mal2zNZTuzGRaYHjaCzC4Oe3+m1df19oi4hsjP4MGqkM0Pxm3B4YizJhiJ+kM X-Received: by 2002:a17:902:2f43:: with SMTP id s61-v6mr14314951plb.176.1538115912244; Thu, 27 Sep 2018 23:25:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538115912; cv=none; d=google.com; s=arc-20160816; b=g1I9Au4+6Ks7VQWc8y5Hxc4dRT36FvFG78a9qXtpHWesU1/5w2Gcu1KPN8IyJmBOdx fw3dRVsjnrGG4/I1ity6/zYjU3HoqoipzAe0HpjoDOJnI14+YUjCWV3YBNWuSSN9Yiqe 3+pQH+OqwUfRNoOH4XOR91QkDUJEJYXba5Hx4G2pd1TJXyI2jPYzNVd8zRG1hIm8GQmk tUr8RbdDEfW3nQk+VDCZQ1+TRHQn2fMb/wCC0ixMxq52q/KIvM7ncnIdd4A35mSjkvhh GYyF5UayIjOCwr5My526yhTbYCY5obNwBX+MnKl45mXa+p8LdThBel6NoIHJumaFplWc r7/w== 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=5lmkQYnv8eJ4VMM0KZ2z4jc7kP/DvENcf8D3l2lSlEA=; b=sWoRlG/LMjb1plNj8i2xujGh689y9av23Z+mvf+q9Au6VlDZzTgZKHKu94CeJE1h4m mHXXdvFEtuOvnoC1UqvLHiL9A/SikoWiuZa01E5tXOHxVJlPCPqLHBlz5HgC6X2HqNR1 3O/XL/hZLzML/6TrPlHYTkvL4s7inqfdWyDhNN54OFYDM5tbKnH0oW++IVmLlTlcYgZI nLtP5BsNL5N2N2RpdyYdRkUA8XnxMl5BbxHjO0PoC47hEIsBIsZycS2q5oY3RUA7HWJt ynHK7a8gMBaRwpTn+lcRbwB+4bxnrsA9RXV3UQcRJFIeh+XgSxqDTBWH5NsPibR7y1Ik nUiw== 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 e6-v6si4002677plt.152.2018.09.27.23.24.56; Thu, 27 Sep 2018 23:25:12 -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 S1728804AbeI1Mq6 (ORCPT + 99 others); Fri, 28 Sep 2018 08:46:58 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:53462 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726068AbeI1Mq6 (ORCPT ); Fri, 28 Sep 2018 08:46:58 -0400 Received: from p5492e4c1.dip0.t-ipconnect.de ([84.146.228.193] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1g5mCi-0001Nw-HM; Fri, 28 Sep 2018 08:24:44 +0200 Date: Fri, 28 Sep 2018 08:24:44 +0200 (CEST) From: Thomas Gleixner To: Andy Lutomirski cc: x86@kernel.org, Peter Zijlstra , Ingo Molnar , Darren Hart , LKML , linux-s390@vger.kernel.org, Martin Schwidefsky , Heiko Carstens , Finn Thain , Geert Uytterhoeven Subject: Re: [PATCH] futex: Set USER_DS for the futex_detect_cmpxchg() test In-Reply-To: Message-ID: References: <74fb6ce22f62e0fb48b91ca9918b74cedbcecaf1.1538096323.git.luto@kernel.org> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) 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 Fri, 28 Sep 2018, Thomas Gleixner wrote: > On Thu, 27 Sep 2018, Andy Lutomirski wrote: > > I have a couple questions here: > > > > - Is this actually okay on all architectures? That is, are there > > cases where we'll screw up if we fail a USER_DS access this early? > > s390 stands out as the obvious special case (where USER_DS is not > > than just a subset of KERNEL_DS), but s390 opts out. > > > > - Why doesn't x86 set HAVE_FUTEX_CMPXCHG? Or do we still support > > some 32-bit configurations that don't have cmpxchg and don't know > > about it at compile time? > > I'm not entirely sure. Have to dig into the details. I assume S390 just can > set it though. x86 as well. It's supported from 486 onwards and we ripped out 386 years ago. Thanks, tglx