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: > > 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.gd9...@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/5f66def673547b7d1e7 > > a841937fbd0ab10a925a0 > > 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. Regards, Salvatore
