linux_4.9.168-1+deb9u2_multi.changes ACCEPTED into proposed-updates->stable-new

Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 May 2019 21:59:18 +0100 Binary: linux-doc-4.9 linux-headers-4.9.0-9-common linux-headers-4.9.0-9-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-9

Processed: found 928989 in 4.9.168-1

Processing commands for cont...@bugs.debian.org: > found 928989 4.9.168-1 Bug #928989 {Done: Salvatore Bonaccorso } [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Marked as found in versions linux/4.9.168-1. > thanks Stopping processing here. Please contact me if you need assistance. --

linux_4.19.37-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 May 2019 17:34:37 +0100 Source: linux Architecture: source Version: 4.19.37-2 Distribution: unstable Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 928618 Changes: linux

Processed: closing 928989

Processing commands for cont...@bugs.debian.org: > close 928989 4.19.37-1 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Ignoring request to alter fixed versions of bug #928989 to the same values previously set Bug #928989 [src:linux] linux-image-4.19.0-4-amd64:

Processed: Re: Bug#928989: linux-image-4.19.0-4-amd64: CVE-2019-11815

Processing control commands: > fixed -1 4.19.37-1 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Marked as fixed in versions linux/4.19.37-1. > found -1 4.9.168-2 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 The source 'linux' and version '4.9.168-2' do

Bug#928989: linux-image-4.19.0-4-amd64: CVE-2019-11815

Control: fixed -1 4.19.37-1 Control: found -1 4.9.168-2 Control: found -1 3.16.64-2 Control: severity -1 important On Tue, 2019-05-14 at 14:37 -0400, Jeff Cliff wrote: > Package: src:linux > Version: 4.19.28-2 > Severity: grave > Tags: security > Justification: user security hole > > Dear

Processing of linux_4.19.37-2_source.changes

linux_4.19.37-2_source.changes uploaded successfully to localhost along with the files: linux_4.19.37-2.dsc linux_4.19.37-2.debian.tar.xz linux_4.19.37-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#928618: marked as done (linux: autopkgtest regression)

Your message dated Tue, 14 May 2019 18:51:16 + with message-id and subject line Bug#928618: fixed in linux 4.19.37-2 has caused the Debian Bug report #928618, regarding linux: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: Re: linux-image-4.19.0-4-amd64: CVE-2019-11815

Processing commands for cont...@bugs.debian.org: > severity 928989 important Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 928989:

Bug#928989: linux-image-4.19.0-4-amd64: CVE-2019-11815

Package: src:linux Version: 4.19.28-2 Severity: grave Tags: security Justification: user security hole Dear Maintainer, An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the Linux kernel before 5.0.8. There is a race condition leading to a use-after-free, related to net

Processed: reassign 901389 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 901389 src:linux 4.19.37-1 Bug #901389 [src:linux] [firmware-iwlwifi] Crash when using as a hotspot with intense usage Ignoring request to reassign bug #901389 to the same package Bug #901389 [src:linux] [firmware-iwlwifi] Crash when

Bug#901389: [firmware-iwlwifi] Crash when using as a hotspot with intense usage

Package: src:linux Version: 4.19.37-1 Severity: important Dear Maintainer, I use another version of linux in my debian box,but I also have totally the same problem when I use my laptop as a hotspot. I attached crash log filename="crash.log" in this report. This problem is randomly and often

Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

On Tue, 2019-05-14 at 13:57 +0100, Ben Hutchings wrote: > Does user-mode-linux need to be a separate source package at all? I guess it is separate to not require building yet another variant. Looks like merging it was discussed in 2016: https://bugs.debian.org/837920 -- bye, pabs

Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

Control: notforwarded -1 On Tue, 2019-05-14 at 14:36 +0530, Ritesh Raj Sarraf wrote: > I submitted this fix upstream to the kernel some time ago. I don't > recollect if the 4.19 kernel is what had it included. > >

Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

On Tue, 2019-05-14 at 18:13 +0530, Ritesh Raj Sarraf wrote: > On Tue, 2019-05-14 at 10:45 +0100, Ben Hutchings wrote: > > > Irrespective, I think it is a fair candidate to be backported if > > 4.19 > > > missed that window. For User-Mode-Linux, The sources are the same > > that > > > the Debian

Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

On Tue, 2019-05-14 at 10:45 +0100, Ben Hutchings wrote: > > Irrespective, I think it is a fair candidate to be backported if > 4.19 > > missed that window. For User-Mode-Linux, The sources are the same > that > > the Debian Linux kernel team maintains. So either they could pick > this > > commit

Re: [PATCH] um: Don't hardcode path as it is architecture dependent

On Tue, May 14, 2019 at 04:36:38PM +0530, Ritesh Raj Sarraf wrote: > Hello Greg, > > On Tue, 2019-05-14 at 12:26 +0200, Greg KH wrote: > > On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote: > > > The current code fails to run on amd64 because of hardcoded > > > reference to > > >

Re: [PATCH] um: Don't hardcode path as it is architecture dependent

Hello Greg, On Tue, 2019-05-14 at 12:26 +0200, Greg KH wrote: > On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote: > > The current code fails to run on amd64 because of hardcoded > > reference to > > i386 > > > > Signed-off-by: Ritesh Raj Sarraf > > Signed-off-by: Richard

Re: [PATCH] um: Don't hardcode path as it is architecture dependent

On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote: > Dear Stable Team, > Request for inclusion into the stable branches of Linux. This change > went into 4.20 but 4.19 is the LTS release that many of the Linux > Vendors are rebasing on. Hence, it'd be nice to see this part of the

[PATCH] um: Don't hardcode path as it is architecture dependent

Dear Stable Team, Request for inclusion into the stable branches of Linux. This change went into 4.20 but 4.19 is the LTS release that many of the Linux Vendors are rebasing on. Hence, it'd be nice to see this part of the LTS releases, at least 4.19. The current code fails to run on amd64

Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

On Tue, 2019-05-14 at 14:36 +0530, Ritesh Raj Sarraf wrote: > Control: tag -1 +fixed-upstream > > CC: Adding Debian Kernel Maintainers > > > Hello Paul, > > I submitted this fix upstream to the kernel some time ago. I don't > recollect if the 4.19 kernel is what had it included. It went into

Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper

Control: tag -1 +fixed-upstream CC: Adding Debian Kernel Maintainers Hello Paul, I submitted this fix upstream to the kernel some time ago. I don't recollect if the 4.19 kernel is what had it included.