From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DB23D3857BA3; Fri, 15 Mar 2024 10:02:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DB23D3857BA3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710496963; bh=I/3BK+qV391QaaTlsHTYBZTVCfw9K5Mn3J9xvdgRfQY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=odwndkhkxXmJgLB9Bn62xNIH64GGgAHGn0plMwVRE7PkDfpADFYCM88uQPjwvW9H4 QBglBMCaZoEzap45Cr7K5N7cHgbX4MLeKqDVJzXyKKLWATXY4xCPWJWFZMW8hIUP6M 0XhLMUVUlQtBXiM1SsR8S4PV2z6vO83pl5K7/BT4= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/113430] [11/12/13 only] Trivial program segfaults intermittently with ASAN with large CONFIG_ARCH_MMAP_RND_BITS in kernel configuration Date: Fri, 15 Mar 2024 10:02:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 13.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113430 --- Comment #12 from Xi Ruoyao --- (In reply to Dimitrij Mijoski from comment #8) > This bug manifested at large on Github Actions CI/CI system in the last f= ew > days most likely because Ubuntu's kernel also got updated to use 32 random > bits. Here is the bug report > https://github.com/actions/runner-images/issues/9491 . It would be a good > idea to backport the fix. But then backporting the fix here won't really help because Ubuntu is not building GCC from the upstream release branch. Ubuntu maintainers could ju= st apply the patch downstream when they decide to increase random bits anyway,= not sure why they didn't.=