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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 60D3FC433EF for ; Fri, 13 May 2022 02:32:23 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4Kzt2s4dFdz3cJD for ; Fri, 13 May 2022 12:32:21 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=WiRAD0gc; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=2604:1380:4641:c500::1; helo=dfw.source.kernel.org; envelope-from=bugzilla-daemon@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=WiRAD0gc; dkim-atps=neutral Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Kzt246L33z2xKK for ; Fri, 13 May 2022 12:31:40 +1000 (AEST) 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 65670620F4 for ; Fri, 13 May 2022 02:31:35 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id C2D98C385B8 for ; Fri, 13 May 2022 02:31:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1652409094; bh=lrl7pwaqDgPgSjg56XA3YDrCz7Vw8u7QbMBkkr96C9w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WiRAD0gcPjwZAZ9kPlRp5BsAJ7JCfDWN7SlTUJEblpcbyIMqnehzfTAgKq9f4jRPX /CsAyEI3icqTKpNHkrve3//ZzecZKpKKjWi3kYVqLyGWUIiE8GyIC+QmRhyw3pb2Nx wPmw41n9vEc2giU6XfKzMx+CLbY7T/ahzJJoL7LbIxhLJ9++AR/OiJGJcR0Tx+KdzR gk8TvXzfd0it2orjwgzhGQBiq922GRaNZiPmcBFh6x0tfhsqcZ/whJzbxpuHe0pSou sL/yAk5QfXUiryqrYdL3FNSH5zRFw/1BkHZRs/O1iGt++NIp4/ssu5/EAQeZYAATq+ OZayWro+D4eEg== Received: by aws-us-west-2-korg-bugzilla-1.web.codeaurora.org (Postfix, from userid 48) id A1975C05FD2; Fri, 13 May 2022 02:31:34 +0000 (UTC) From: bugzilla-daemon@kernel.org To: linuxppc-dev@lists.ozlabs.org Subject: [Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite Date: Fri, 13 May 2022 02:31:34 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo platform_ppc-32@kernel-bugs.osdl.org X-Bugzilla-Product: Platform Specific/Hardware X-Bugzilla-Component: PPC-32 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: michael@ellerman.id.au X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: platform_ppc-32@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" https://bugzilla.kernel.org/show_bug.cgi?id=3D215389 Michael Ellerman (michael@ellerman.id.au) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |michael@ellerman.id.au --- Comment #21 from Michael Ellerman (michael@ellerman.id.au) --- Increasing the stack size (CONFIG_THREAD_SHIFT) might avoid the stack overf= lows and allow you to debug the original issue in isolation. --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=