From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E28BB3853576; Tue, 30 Aug 2022 09:15:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E28BB3853576 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1661850928; bh=64EvsyfSQ1oFNmAHWGeOE3kxgrVFkG2f/QnVANGqiuA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jmepz2o7dXQ+mgUHSQcW9Eq+xC0GE11RkV5xmS46NF8QaW8ZTu3vdNNApmGBEfgSl JGzV+AfdCa3AHAzo9Nt7hg7Fh94TiMg2GfJS1SNKi9g6+u3WhBNy5wl7ZJayCjl3Qm Td/Bcp88H6DmIjLODncrEc4SapPZtfx1dbqM8oGI= From: "glaubitz at physik dot fu-berlin.de" To: glibc-bugs@sourceware.org Subject: [Bug libc/29537] [2.34 regression]: Alignment issue on m68k when using futexes on qemu-user Date: Tue, 30 Aug 2022 09:15:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.34 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- 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://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29537 --- Comment #1 from John Paul Adrian Glaubitz --- I can confirm that the following change fixes the problem for me: --- glibc-2.34.orig/sysdeps/nptl/libc-lockP.h +++ glibc-2.34/sysdeps/nptl/libc-lockP.h @@ -34,7 +34,7 @@ #include /* Mutex type. */ -typedef int __libc_lock_t; +typedef int __libc_lock_t __attribute__((aligned(4))); typedef struct { pthread_mutex_t mutex; } __rtld_lock_recursive_t; typedef pthread_rwlock_t __libc_rwlock_t; However, I am not sure whether it will have any negative side effects like breaking the ABI. --=20 You are receiving this mail because: You are on the CC list for the bug.=