Processed: Bug#1030200: adding linux-image-6.1.0-7-amd64 to affects

2023-03-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1030200 + linux-image-6.1.0-7-amd64 Bug #1030200 [src:linux] linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable Added indication that 1030200 affects linux-ima

Bug#1030200: linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable

2023-03-24 Thread наб
If anyone has a faintest idea so as to what the problem may be, please help; the only vaguely-related config change is INTEGRITY_MACHINE_KEYRING going from unset to y, but that shouldn't(! not that it doesn't, the code is an enigma to me, but as i understand it and as i read the kconfig, it should

Bug#1030200: linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable

2023-03-24 Thread наб
Control: found -1 6.1.20-1 Updated to linux-image-6.1.0-7-amd64 (6.1.20-1); still happens. наб Mar 25 01:38:54 babtop kernel: microcode: microcode updated early to revision 0xf4, date = 2022-07-31 Mar 25 01:38:54 babtop kernel: Linux version 6.1.0-7-amd64 (debian-kernel@lists.debian.org) (gcc-1

Processed: Re: Bug#1030200: linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable

2023-03-24 Thread Debian Bug Tracking System
Processing control commands: > found -1 6.1.20-1 Bug #1030200 [src:linux] linux-image-6.1.0-3-amd64: "Loading of module with unavailable key is rejected", /proc/keys says key is loaded; system unbootable Marked as found in versions linux/6.1.20-1. -- 1030200: https://bugs.debian.org/cgi-bin/bug

Bug#1032642: iproute2: ip tunnel change ip6gre to gre crashes with stack smash

2023-03-24 Thread Bernhard Übelacker
Dear Maintainer, I tried to find out where exactly the stack smashing takes place. And found the ioctl SIOCCHGTUNNEL did write more than the 52 bytes allocated in variable old_p, by that overwriting the stack canary. Kind regards, Bernhard (gdb) 0x5557589f 62 { 1: x/i $pc => 0

Bug#1033301: linux: arm64 kernel size increased from 31 to 39 MB, causing u-boot-rpi to fail

2023-03-24 Thread Vagrant Cascadian
Adding u-boot maintainers for rpi (Matthias Brugger, Peter Robinson) platforms and u-boot list to CC. On 2023-03-22, Salvatore Bonaccorso wrote: > Thanks for tracking this down. I would like to loop in Masahiro and > upstream to see if something can/should be done on upstream side. > > Masahiro, i

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

2023-03-24 Thread Florian Lehner
Hi, maybe some additional information. The eBPF program is of type BPF_PROG_TYPE_PERF_EVENT and attached to all CPUs via the perf subsystem and the use of PERF_COUNT_SW_CPU_CLOCK. It is executed on a constant sampling frequency (usually 20 Hz). We also do have qemus guest memory dumps availa

Processed: Re: Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

2023-03-24 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 6.1.20-1 Bug #1033398 [linux-image-amd64] linux-image-amd64: reproducible kernel freeze on 5.19+ Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.1.20+1. Ignoring request

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

2023-03-24 Thread Diederik de Haas
Control: reassign -1 src:linux 6.1.20-1 On Friday, 24 March 2023 12:44:33 CET Tim Rühsen wrote: > Package: linux-image-amd64 > Version: 6.1.20-1 > > We run a priviledged eBPF based tool with a communication between kernel and > user space. It runs without issues on kernels 4.15 to 5.18. > On kern

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

2023-03-24 Thread Tim Rühsen
Package: linux-image-amd64 Version: 6.1.20-1 Severity: important X-Debbugs-Cc: tim.rueh...@gmx.de Dear Maintainer, * What led up to the situation? We run a priviledged eBPF based tool with a communication between kernel and user space. It runs without issues on kernels 4.15 to 5.18. On kerne