linux-signed-amd64_6.1.12+1_source.changes is NEW

Mapping sid to unstable. binary:acpi-modules-6.1.0-5-amd64-di is NEW. binary:ata-modules-6.1.0-5-amd64-di is NEW. binary:btrfs-modules-6.1.0-5-amd64-di is NEW. binary:cdrom-core-modules-6.1.0-5-amd64-di is NEW. binary:crc-modules-6.1.0-5-amd64-di is NEW. binary:crypto-dm-modules-6.1.0-5-amd64-di is

Processing of linux-signed-amd64_6.1.12+1_source.changes

linux-signed-amd64_6.1.12+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_6.1.12+1.dsc linux-signed-amd64_6.1.12+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1031356: pinctrl: linux-image-6.1.0-3-amd64 : kernel NULL pointer dereference with intel pinctrl driver

Hi, On Wed, Feb 15, 2023 at 04:53:49PM +0100, Frederic Buisson wrote: > Package: src:linux > Version: 6.1.8-1 > Severity: important > File: pinctrl > X-Debbugs-Cc: frederic.buis...@f-g.fr > > Dear Maintainer, > > The problem appears at boot time : > > [1.582787] BUG: kernel NULL pointer deref

Bug#1031356: pinctrl: linux-image-6.1.0-3-amd64 : kernel NULL pointer dereference with intel pinctrl driver

On Wednesday, 15 February 2023 16:53:49 CET Frederic Buisson wrote: > Package: src:linux > Version: 6.1.8-1 > Severity: important > File: pinctrl Please try the 6.1.12-1 version when it becomes available to you. There are several pinctrl fixes in that version. signature.asc Description: This is a

Bug#1031356: pinctrl: linux-image-6.1.0-3-amd64 : kernel NULL pointer dereference with intel pinctrl driver

Package: src:linux Version: 6.1.8-1 Severity: important File: pinctrl X-Debbugs-Cc: frederic.buis...@f-g.fr Dear Maintainer, The problem appears at boot time : [1.582787] BUG: kernel NULL pointer dereference, address: [1.582816] #PF: supervisor read access in kernel mod

[PATCH v3] s390/signal: fix endless loop in do_signal

No upstream commit exists: the problem addressed here is that 'commit 75309018a24d ("s390: add support for TIF_NOTIFY_SIGNAL")' was backported to 5.10. This commit is broken, but nobody noticed upstream, since shortly after s390 converted to generic entry with 'commit 56e62a737028 ("s390: convert

[PATCH v2 1/1] s390/signal: fix endless loop in do_signal

No upstream commit exists: the problem addressed here is that 'commit 75309018a24d ("s390: add support for TIF_NOTIFY_SIGNAL")' was backported to 5.10. This commit is broken, but nobody noticed upstream, since shortly after s390 converted to generic entry with 'commit 75309018a24d ("s390: add sup

Re: [PATCH 0/1] s390: fix endless loop in do_signal

On Wed, Feb 15, 2023 at 02:35:24PM +0100, Heiko Carstens wrote: > On Wed, Feb 15, 2023 at 02:23:20PM +0100, Greg KH wrote: > > On Wed, Feb 15, 2023 at 01:04:12PM +0100, Sumanth Korikkar wrote: > > > Hi, > > > > > > This patch fixes the issue for s390 stable kernel starting 5.10.162. > > > The is

Re: [PATCH 0/1] s390: fix endless loop in do_signal

On Wed, Feb 15, 2023 at 02:23:20PM +0100, Greg KH wrote: > On Wed, Feb 15, 2023 at 01:04:12PM +0100, Sumanth Korikkar wrote: > > Hi, > > > > This patch fixes the issue for s390 stable kernel starting 5.10.162. > > The issue was specifically seen after stable version 5.10.162: > > Following commi

Re: [PATCH 0/1] s390: fix endless loop in do_signal

On Wed, Feb 15, 2023 at 01:04:12PM +0100, Sumanth Korikkar wrote: > Hi, > > This patch fixes the issue for s390 stable kernel starting 5.10.162. > The issue was specifically seen after stable version 5.10.162: > Following commits can trigger it: > 1. stable commit id - 788d0824269b ("io_uring: i

Re: [PATCH 1/1] s390/signal: fix endless loop in do_signal

On Wed, Feb 15, 2023 at 01:04:13PM +0100, Sumanth Korikkar wrote: > No upstream commit exists. Why not? Please explain how this was fixed in Linus's tree and why we can't take the same change here as well. thanks, greg k-h

[PATCH 1/1] s390/signal: fix endless loop in do_signal

No upstream commit exists. Thread flag is set to TIF_NOTIFY_SIGNAL for io_uring work. The io work user or syscall calls do_signal when either one of the TIF_SIGPENDING or TIF_NOTIFY_SIGNAL flag is set. However, do_signal does consider only TIF_SIGPENDING signal and ignores TIF_NOTIFY_SIGNAL cond

[PATCH 0/1] s390: fix endless loop in do_signal

Hi, This patch fixes the issue for s390 stable kernel starting 5.10.162. The issue was specifically seen after stable version 5.10.162: Following commits can trigger it: 1. stable commit id - 788d0824269b ("io_uring: import 5.15-stable io_uring") can trigger this problem. 2. upstream commit id -

linux_6.1.12-1_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Feb 2023 06:56:21 +0100 Source: linux Architecture: source Version: 6.1.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvato

Bug#1029584: marked as done (linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config)

Your message dated Wed, 15 Feb 2023 08:10:10 + with message-id and subject line Bug#1029584: fixed in linux 6.1.12-1 has caused the Debian Bug report #1029584, regarding linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config to be marked as done. This mean

Bug#993612: marked as done (bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye)

Your message dated Wed, 15 Feb 2023 08:10:10 + with message-id and subject line Bug#993612: fixed in linux 6.1.12-1 has caused the Debian Bug report #993612, regarding bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye to be marked as done. This means that y