Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp317683rwr; Thu, 27 Apr 2023 01:31:44 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4DjZF3gdHLRPsDMSZP4suGJ6FWhia4DaHnc2R9Zn7sMJeLX4hbv4IJBY8NkzpGlxOOfyFQ X-Received: by 2002:a17:902:eccf:b0:1a9:465c:6802 with SMTP id a15-20020a170902eccf00b001a9465c6802mr892197plh.5.1682584303940; Thu, 27 Apr 2023 01:31:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682584303; cv=none; d=google.com; s=arc-20160816; b=jBrwXabAmd++vOOAP0rLId8HWqRhKwo+6sgBx0EL9fwqsSSOnlITiZUuPNHIkdrOGw 70ujrvSEFTnQj2T/Dh6sO2YpOo66QpOqRxtMS+l89KyYRpolOMUKVHYKVRdrDBvNEdUs TBvLXml1wfRM79PuUt66qY8alrGp3mW6fnyHBOc+nqEfVaIkpXK4z5qMLtbainaltaxi Li+X3iyrDxjKTDM63vMnlLlmGzpC6pgZYQhGp9pl7jp0l0PMB/+6nc2WSVmtBGYy2M6/ uZ3crWE+qtfWkNxQV94rh80d/ZYQx8bB4N2FZ/wVNkReMDQHTRVaXe4F9lMFuxMojIRB rTHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=LtR2k/yBu8x2u9SZRcF1XiK62JEmxJW//gKr+bgIUCU=; b=QRCimzhLMts9G75w0Bk3LzFZLa459AJVmlJMR7OapAp5vgj17VfClQxGIdIY5Cbtyd +cQHSv7y3ol8h+goxs2P9NSsf6FhhVGWxwRtRMnJAKWErwmHycsISs5MqJx8IjI/o3Pq vR9knmhXlG1YEg/9kwGs5JY1INhxfbBSS2OOhd78frLuBp2iBK5D6JqcnZV+ML+FAcWL vzoOo6EeKJBtlxqMnoGCH6yvf2rRU8B5G94S7M0oVbnKXfTH9DxmYCE8K/ZsldxBMjFK hj+ZA3nLs5M1LJgnGoT5Juc0N2DNWZE7oFDbRulB2SP3ejiB8U3Td6+4qasoj29B83wz yuew== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=DnWrxOYe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s12-20020a170902ea0c00b001a97bf417cdsi9890764plg.571.2023.04.27.01.31.30; Thu, 27 Apr 2023 01:31:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=DnWrxOYe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243100AbjD0Ia7 (ORCPT + 99 others); Thu, 27 Apr 2023 04:30:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44434 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243044AbjD0Ia5 (ORCPT ); Thu, 27 Apr 2023 04:30:57 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1845635A6; Thu, 27 Apr 2023 01:30:56 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9FAB263B95; Thu, 27 Apr 2023 08:30:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B45CFC433D2; Thu, 27 Apr 2023 08:30:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1682584255; bh=IjxCeFXNKWQY8KVcSMtLu5/gGhTGtBIACEOnd4UUKAY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=DnWrxOYe0uv6FWThGph9NFDloKu5HSdxqADr2R2ACQAoVF9AKj/K04MBdUrKI6NeA 1jvnvbsfsYNxW7wYtnLOOrza9gQK0Yt5O8XPasYy3PavJ9B9ubsXyXHdU/3kdVgmx7 UOeOMN9DxOSWld/wjXnWg4dPf9s1NYn/Pkh1I3yU= Date: Thu, 27 Apr 2023 10:30:52 +0200 From: Greg KH To: SeongJae Park Cc: Sasha Levin , linux-kernel@vger.kernel.org, stable@vger.kernel.org, David Gow , Sergio =?iso-8859-1?Q?Gonz=E1lez?= Collado , Richard Weinberger , tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org Subject: Re: [PATCH AUTOSEL 6.1 04/13] rust: arch/um: Disable FP/SIMD instruction to match x86 Message-ID: <2023042745-unclasp-briar-5b2a@gregkh> References: <20230314124325.470931-4-sashal@kernel.org> <20230425000118.45838-1-sj@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230425000118.45838-1-sj@kernel.org> X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 25, 2023 at 12:01:18AM +0000, SeongJae Park wrote: > Hello Sasha and Greg, > > > On Tue, 14 Mar 2023 08:43:16 -0400 Sasha Levin wrote: > > > From: David Gow > > > > [ Upstream commit 8849818679478933dd1d9718741f4daa3f4e8b86 ] > > > > The kernel disables all SSE and similar FP/SIMD instructions on > > x86-based architectures (partly because we shouldn't be using floats in > > the kernel, and partly to avoid the need for stack alignment, see: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53383 ) > > > > UML does not do the same thing, which isn't in itself a problem, but > > does add to the list of differences between UML and "normal" x86 builds. > > > > In addition, there was a crash bug with LLVM < 15 / rustc < 1.65 when > > building with SSE, so disabling it fixes rust builds with earlier > > compiler versions, see: > > https://github.com/Rust-for-Linux/linux/pull/881 > > > > Signed-off-by: David Gow > > Reviewed-by: Sergio Gonz?lez Collado > > Signed-off-by: Richard Weinberger > > Signed-off-by: Sasha Levin > > There is a followup fix of this patch that merged into the mainline by commit > a3046a618a28 ("um: Only disable SSE on clang to work around old GCC bugs"), but > it has not added to 6.1.y so far. Without it, compiling on some setup using an > old version of gcc fails, as the followup is also mentioning. I also confirmed > the issue can be reproduced on latest 6.1.y. > > Could you please add the followup fix to 6.1.y? I confirmed the commit can be > cleanly cherry-picked on latest 6.1.y, and fixes the issue as expected. Now queued up, thanks. greg k-h