From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2540C433F5 for ; Thu, 24 Feb 2022 03:59:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229840AbiBXD7c (ORCPT ); Wed, 23 Feb 2022 22:59:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41158 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229770AbiBXD73 (ORCPT ); Wed, 23 Feb 2022 22:59:29 -0500 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 49FBE25F344 for ; Wed, 23 Feb 2022 19:59:00 -0800 (PST) Received: by mail-pl1-x62c.google.com with SMTP id bd1so595055plb.13 for ; Wed, 23 Feb 2022 19:59:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ipcMbOhFS/2FiJEFtsW19b67QSx/DKh4wGATjCAKrkY=; b=ZnawhkpDqU+rZlOg1P0cBGB0T65BAaTadLRW1leM/SrFFGbp0E9ZJ3/bJH3dhqPAcm pQpEqo/A7vpTuh9ApxtdE0+Q4YuYDWgqFar+s/Iao8+jjt3Uuz5ySEP3Sv8h8VmG/zcc 1ARH9+FZTnmavgiFljrm2KxQ8Wy3OsIlx+FLM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ipcMbOhFS/2FiJEFtsW19b67QSx/DKh4wGATjCAKrkY=; b=oGjuYt+zWmRfakAh36c1tnLgBobEegK0s/nBytVnf19kN1IPA9c2X0a7Xf9BlmTQ7U emuaJhbdVlYxnAyRtF9NpGY6TfbwqkrW1VE6pIEanYUMho3ziIT5Oo5FyDlf495fFuvp MKJrmC6YPzJ6yHG8rN1zsMAVT/ibnpA8XlcVYiHLetyubhCFPu1DRernf8n9w7BLRfqd K2hQdIOcz48GXbCF4YVh742e9b0Xdw9FWRBbP1u697QTrMua/rq4EZxrow4aDMy5d+nQ rlbzlSQH+XJJRC0JrJBG4uMvb1TEcgLmTxp2fIOyjN02C238ss46TnR2dktJXX3nBPcQ QhZQ== X-Gm-Message-State: AOAM530/3x5RJo4U70T83DmR5pvNLBXiAWR7/0Dzum9Q42GrjOYykl6g BtBDGVjSCqgHGbfq2rOivfMZXw== X-Google-Smtp-Source: ABdhPJzn1uMQcYSD5vqES/uqQG8fcX1txbzlrszEOeO34PcIjg+0QC/31asHtN0y0pT/5plGU0HyDA== X-Received: by 2002:a17:902:f606:b0:14b:4c2d:e1fa with SMTP id n6-20020a170902f60600b0014b4c2de1famr889815plg.24.1645675139788; Wed, 23 Feb 2022 19:58:59 -0800 (PST) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id z13sm1146016pfe.20.2022.02.23.19.58.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Feb 2022 19:58:59 -0800 (PST) Date: Wed, 23 Feb 2022 19:58:58 -0800 From: Kees Cook To: John Paul Adrian Glaubitz Cc: Thorsten Leemhuis , Anthony Yznaga , matoro_bugzilla_kernel@matoro.tk, Andrew Morton , "regressions@lists.linux.dev" , linux-ia64@vger.kernel.org, Linux-fsdevel , Linux Kernel Mailing List , Alexander Viro Subject: Re: regression: Bug 215601 - gcc segv at startup on ia64 Message-ID: <202202231957.801F1780@keescook> References: <823f70be-7661-0195-7c97-65673dc7c12a@leemhuis.info> <03497313-A472-4152-BD28-41C35E4E824E@chromium.org> <94c3be49-0262-c613-e5f5-49b536985dde@physik.fu-berlin.de> <9A1F30F8-3DE2-4075-B103-81D891773246@chromium.org> <4e42e754-d87e-5f6b-90db-39b4700ee0f1@physik.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4e42e754-d87e-5f6b-90db-39b4700ee0f1@physik.fu-berlin.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 21, 2022 at 10:57:01PM +0100, John Paul Adrian Glaubitz wrote: > Hi Kees! > > On 2/21/22 21:58, Kees Cook wrote: > >> I have applied this patch on top of 038101e6b2cd5c55f888f85db42ea2ad3aecb4b6 and it doesn't > >> fix the problem for me. Reverting 5f501d555653f8968011a1e65ebb121c8b43c144, however, fixes > >> the problem. > >> > >> FWIW, this problem doesn't just affect GCC but systemd keeps segfaulting with this change as well. > > > > Very weird! Can you attached either of those binaries to bugzilla (or a URL I can fetch it from)? I can try to figure out where it is going weird... > > Here's the initrd of that particular machine: > > > https://people.debian.org/~glaubitz/initrd.img-5.17.0-rc5+ > > You should be able to extract the binaries from this initrd image and the "mount" command, > for example, should be one of the affected binaries. I don't see anything immediately obvious here, but I'll keep looking. Is there any way to emulate ia64? I don't see anything that'll work under QEMU... -- Kees Cook