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

Bug#928465: marked as done (stretch-pu: package linux/4.9.168-1)

Your message dated Wed, 15 May 2019 12:36:52 +0100
with message-id <b1d4bfa7063902d9c4ae2f928a7ae893@mail.adam-barratt.org.uk>
and subject line Re: Bug#928465: stretch-pu: package linux/4.9.168-1
has caused the Debian Bug report #928465,
regarding stretch-pu: package linux/4.9.168-1
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.)


-- 
928465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928465
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: pu

Hi stable release managers,

The last linux upload via the stretch point release unfortunately
uncovered #928125, easily triggerble when forcing the kernel to scan
the partition table on a newly created loop device.

In the upstream development of the 4.9 series between the 4.9.140
upload in the previous stretch point release, some backports to
changes related to the loopback were  again later reverted due to
regressions.

One commit though was keept up to 4.9.168, which relates to the thread
in 
https://lore.kernel.org/stable/20190320125806.GD9485@quack2.suse.cz/ .

I seek input/advice/opinion from you stable release managers: Do you
want to issue a SUA and fast-track a fix for this issue via
stretch-updates?

For completeness, the isolated revert is at
https://salsa.debian.org/kernel-team/linux/commit/5f66def673547b7d1e7a841937fbd0ab10a925a0
.

If not, the issue would be fixed when rebasing to the 4.9.173 or later
kernel as well, work for that is ongoin as well in
https://salsa.debian.org/kernel-team/linux/merge_requests/141 .

Ideally kernels which are pending for a point relase and which we
upload in advance for the point release seem to not get as much wider
testing as it would make such regressions reported after the point
release less frequent, I do not have a good proposal for that though.

Regards,
Salvatore

--- End Message ---
--- Begin Message --- 
On 2019-05-14 19:40, Salvatore Bonaccorso wrote:

Hi Adam,

On Thu, May 09, 2019 at 10:04:10PM +0100, Adam D. Barratt wrote:

Control: tags -1 + confirmed

Hi,

Sorry for not picking this up sooner.

On Sun, 2019-05-05 at 11:28 +0200, Salvatore Bonaccorso wrote:

[...]
Let's go with the quicker fix - hopefully the SUA can get released over 
the weekend.


We will "shortly" release a DSA for linux which will include this
regression fix as well, so no furhter action via a SUA would be
needed.
ACK, thanks - closing with this mail. Feel free to do so yourself in such circumstances. :-) 

Regards,

Adam

--- End Message ---
Reply to: