[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#995223: marked as done (libffi: autoconf incompatibility causes baseline violation)

Your message dated Mon, 17 Jan 2022 11:04:00 +0000
with message-id <E1n9Pns-000A57-Di@fasolo.debian.org>
and subject line Bug#995223: fixed in libffi 3.4.2-4
has caused the Debian Bug report #995223,
regarding libffi: autoconf incompatibility causes baseline violation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
995223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995223
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libffi
Version: 3.3-6
Severity: important
User: debian-powerpc@lists.debian.org
Usertags: powerpc ppc64
X-Debbugs-Cc: debian-powerpc@lists.debian.org

Hi!

Multiple users on powerpc and ppc64 have reported SIGILL crashes
after upgrading to libffi8 (3.4.x):

# dmesg
...
[   16.257543] fail2ban-server[384]: illegal instruction (4) at
3fffb4283970 nip 3fffb4283970 lr 3fffb4282f90 code 1 in
libffi.so.8.1.0[3fffb427b000+c000]
...

Downgrading to libffi7 fixes the problem.

It has been reported that building and using the upstream version
does not reproduce this issue. But I have not yet independently
verified that. It might be that libffi performs a runtime detection
during build which causes the library to be built with a higher
baseline on the POWER8 buildds.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

--- End Message ---
--- Begin Message --- 
Source: libffi
Source-Version: 3.4.2-4
Done: Matthias Klose <doko@debian.org>

We believe that the bug you reported is fixed in the latest version of
libffi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 995223@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated libffi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 17 Jan 2022 11:37:08 +0100
Source: libffi
Architecture: source
Version: 3.4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 995223
Changes:
 libffi (3.4.2-4) unstable; urgency=medium
 .
   * Configure --without-gcc-arch. Closes: #995223.
Checksums-Sha1:
 c02b394b978cb000143ac5a66cae352a8aaf5678 1948 libffi_3.4.2-4.dsc
 013d7a9aceed1ebb9924efeb67122a09df5cde0e 8164 libffi_3.4.2-4.debian.tar.xz
 2c23738151d6e8e23e6772dfe53a6438ce924d8e 6260 libffi_3.4.2-4_source.buildinfo
Checksums-Sha256:
 c7c4890a434795e41a77bddbca949fb904b022a70d8446c5a005ec0f9ed4c554 1948 libffi_3.4.2-4.dsc
 06d936d00d43e7999d0bce0aa2e0f1550109295b8093de77e6453acb9eacfd19 8164 libffi_3.4.2-4.debian.tar.xz
 b55b0306bae159c235a768bd4562d2da931e51f85840bd1287c3c826fc4b4747 6260 libffi_3.4.2-4_source.buildinfo
Files:
 bea8ba820578b42151332e57ee8d54c1 1948 libs optional libffi_3.4.2-4.dsc
 10caa25af48e5ccebfe674cfb354121a 8164 libs optional libffi_3.4.2-4.debian.tar.xz
 8d7efc27e884eb69d8cd5c379b37917b 6260 libs optional libffi_3.4.2-4_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmHlR4gQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9dPJD/9c2sGsYNglndxMb0memUb7QzP+tzsqFH6c
sT0UCC3Ro0J24CU+oGd7p8V2g9gcMjM90YkZijgkx5zPGRQLQyqJw9SXfade9Q5v
SY/t/2dH6OqCArFulMsDXE7EH+FzDFNTa4ux777syC0FvMH/8LPcwUUw0FIhKOtR
ML+poswtFF6DEpinwdCexNYLW1C9dJYUp2E5MyAC6KCPtwSPyesnm0P5pc3jQ+in
KQdijhJUB5yHRtzKYIjJOGNIyV7b817YH1KEQWEQtT5aGv9MJ3+kBSFstqVou9Bq
WhO6y87EQEY7WsqNz9dcYFHSjifWcZ9BEkQeOH+xPIrslXaXLPFDkmy3BK0mEguI
T9+U0yKYOdHszofUyEFPH67DYoHVgUagbnkBqBSuVwhrzCp8LK4iRpV1Mzlnv7oW
vy+UTkgfiMcm70UM74scFBhnkQ5AxERSchpSiIqs/tzFVUTyNga324H50UWlqszx
OlomfRR7dSlVLq66gYv5nuw8GYqJXr3Q81OTee8DLYp5PpSb9ED94ZqUe1RZLZd/
ZODJLl/04j5y3PJtjtBY1JOjrUyxa51RvwkNGu29cSgtErG2ye/BiJPrbxBZaSND
IoloOn5fSQvkanEGYZv/2Z8nOZUJvct39HnnHYJfokFq/JNNU24DLH9QVoVlTs1T
RBi0xQxoUg==
=W/bo
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: