linux-kernel - RE: Regression on linux-next (next-20240712)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <SJ1PR11MB612934133B2E0558949BBC29B9AC2@SJ1PR11MB6129.namprd11.prod.outlook.com>
Date: Thu, 18 Jul 2024 05:09:31 +0000
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@...el.com>
To: Andrew Morton <akpm@...ux-foundation.org>, David Hildenbrand
	<david@...hat.com>
CC: "peili.dev@...il.com" <peili.dev@...il.com>, "Nikula, Jani"
	<jani.nikula@...el.com>, "Saarinen, Jani" <jani.saarinen@...el.com>, "Kurmi,
 Suresh Kumar" <suresh.kumar.kurmi@...el.com>,
	"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: RE: Regression on linux-next (next-20240712)



> -----Original Message-----
> From: Andrew Morton <akpm@...ux-foundation.org>
> Sent: Thursday, July 18, 2024 1:31 AM
> To: David Hildenbrand <david@...hat.com>
> Cc: Borah, Chaitanya Kumar <chaitanya.kumar.borah@...el.com>;
> peili.dev@...il.com; Nikula, Jani <jani.nikula@...el.com>; Saarinen, Jani
> <jani.saarinen@...el.com>; Kurmi, Suresh Kumar
> <suresh.kumar.kurmi@...el.com>; intel-gfx@...ts.freedesktop.org; linux-
> mm@...ck.org; linux-kernel@...r.kernel.org
> Subject: Re: Regression on linux-next (next-20240712)
> 
> On Wed, 17 Jul 2024 13:00:58 +0200 David Hildenbrand <david@...hat.com>
> wrote:
> 
> > > Could you please check why the patch causes this regression and provide
> a fix if necessary?
> >
> > This is know.
> >
> > There is a discussion along the original patch [1] on how to do it
> > differently. But likely we'll tackle it differently [2]. So this patch
> > should be dropped for -- which I think already happened because I
> > cannot spot that patch in mm-unstable anymore.
> 
> Yes, I dropped it on July 15.

Thank you. Our CI runs seems to have recovered from the regression.

Regards

Chaitanya