From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6808638425BC; Tue, 30 Aug 2022 07:30:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6808638425BC DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1661844625; bh=SU219CvYNJlOBa4vPfw2TiJXP080fDTFawin1bHvGnI=; h=From:To:Subject:Date:From; b=HvXACZZbs9a2BMD9udCcTsrtTKUY6xOK7GIq5Hk/C5WaheXOuxWVX6LOh2e3mr3NR tLa+2Jb2L4NO3v2Ak0iEgwsOaxRoNdbT/CW9p2FfihyvaIaaoAYmf9VJBpALc54TMs 3yAw17MY2M2WOiXpPgQ7QSY+6q+r7c+AteEAoraU= From: "glaubitz at physik dot fu-berlin.de" To: glibc-bugs@sourceware.org Subject: [Bug libc/29537] New: [2.34 regression]: Alignment issue on m68k when using futexes on qemu-user Date: Tue, 30 Aug 2022 07:30:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost Message-ID: 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 Bug ID: 29537 Summary: [2.34 regression]: Alignment issue on m68k when using futexes on qemu-user Product: glibc Version: 2.34 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: glaubitz at physik dot fu-berlin.de CC: adhemerval.zanella at linaro dot org, drepper.fsp at gm= ail dot com, rth at sourceware dot org, schwab@linux-m68k.org Target Milestone: --- Host: m68k-*-* There is a recent regression when using running a Linux/m68k userland on qemu-user with applications crashing with futex errors: dh_md5sums -a -O--builddirectory=3Dbuild -O--dbgsym-migration=3Daptitude= -dbg dh_builddeb -a -O--builddirectory=3Dbuild -O--dbgsym-migration=3Daptitud= e-dbg dpkg-deb: building package 'aptitude-dbgsym' in '../aptitude-dbgsym_0.8.13-4_m68k.deb'. dpkg-deb: building package 'aptitude' in '../aptitude_0.8.13-4_m68k.deb'. The futex facility returned an unexpected error code. qemu: uncaught target signal 6 (Aborted) - core dumped dpkg-deb: error: from tar -cf subprocess was killed by signal (Aborted) dh_builddeb: error: dpkg-deb --root-owner-group --build debian/.debhelper/aptitude/dbgsym-root .. returned exit code 2 dh_builddeb: error: Aborting due to earlier error make: *** [debian/rules:22: binary-arch] Error 2 The error was reported to QEMU upstream [1] but eventually turned out to be= a glibc problem [2]. According to the comment by Richard Henderson, glibc must enforce the alignment of __libc_lock_t to be 32 bits. > [1] https://gitlab.com/qemu-project/qemu/-/issues/957 > [2] https://gitlab.com/qemu-project/qemu/-/issues/957#note_1081526226 --=20 You are receiving this mail because: You are on the CC list for the bug.=