Processed: found 904385 in linux/4.17.6-2

2018-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 904385 linux/4.17.6-2 Bug #904385 [src:linux] arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes Marked as found in versions linux/4.17.6-2. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed (with 1 error): Re: Bug#904385: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

2018-07-23 Thread Debian Bug Tracking System
Processing control commands: > affects -1 glibc Bug #904385 [src:linux] arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes Added indication that 904385 affects glibc > found linux/4.17.6-2 Unknown command or malformed arguments to command. -- 904385:

Bug#904385: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

2018-07-23 Thread Aurelien Jarno
control: affects -1 glibc control: found linux/4.17.6-2 On 2018-07-23 21:31, Aurelien Jarno wrote: > Package: src:linux > Version: 4.9.110-1 > Severity: normal > > Dear Maintainer, > > The arm64 kernel allows one to run aarch32 processes on an aarch64 > processor (if it has support for it),

Bug#904385: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

2018-07-23 Thread Aurelien Jarno
Package: src:linux Version: 4.9.110-1 Severity: normal Dear Maintainer, The arm64 kernel allows one to run aarch32 processes on an aarch64 processor (if it has support for it), using the standard 32/64-bit syscall compatibility. However this compat layer does not correctly validate the arguments

Re: Status of this bug

2018-07-23 Thread David Goodenough
On Monday, 23 July 2018 14:30:06 BST Lisandro Damián Nicanor Pérez Meyer wrote: > This has happened so far: > > From the Debian side maxy added haveged as a sddm recommendation and as a > workaround. > > From the Qt side Thiago from upstream is trying to determine what changed in > the

Processed: severity of 904057 is important

2018-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 904057 important Bug #904057 [src:linux] linux-image-4.9.0-7-amd64: DMAR errors at boot and erratic ACPI behavior with suspend-to-RAM Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you

Re: Status of this bug

2018-07-23 Thread Lisandro Damián Nicanor Pérez Meyer
On Mon, 23 Jul 2018 at 12:49, Ben Hutchings wrote: > CVE-2018-1108 was fixed in the kernel. Thanks Ben -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Re: Status of this bug

2018-07-23 Thread Ben Hutchings
On Mon, 2018-07-23 at 10:30 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > This has happened so far: > > From the Debian side maxy added haveged as a sddm recommendation and as a > workaround. > > From the Qt side Thiago from upstream is trying to determine what changed in > the kernel

Processed: affects 903776

2018-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 903776 + release.debian.org Bug #903776 [src:linux] Kernel 4.9.110-1 sit: non-ECT warnings Added indication that 903776 affects release.debian.org > thanks Stopping processing here. Please contact me if you need assistance. -- 903776:

Status of this bug

2018-07-23 Thread Lisandro Damián Nicanor Pérez Meyer
This has happened so far: From the Debian side maxy added haveged as a sddm recommendation and as a workaround. From the Qt side Thiago from upstream is trying to determine what changed in the kernel side, as this clearly started to happen with 4.16 and got worse with 4.17. Ben, linux

Bug#902966: pstore: crypto_comp_decompress failed

2018-07-23 Thread Sedat Dilek
Hi, I can confirm to see this on Debian/buster AMD64 with... linux-image-4.17.0-1-amd64 (4.17.8-1) ...and removing all dmesg-efi-*.enc.z files in /sys/fs/pstore/... ...and rebooting made the failures in dmesg go away. Not sure what 'gzip: stdin: unexpected end of file' means exactly in