[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240325113433.e04c2b508ac325630cd113c8@linux-foundation.org>
Date: Mon, 25 Mar 2024 11:34:33 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: "V, Narasimhan" <Narasimhan.V@....com>, "linux-next@...r.kernel.org"
<linux-next@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
"Aithal, Srikanth" <Srikanth.Aithal@....com>, Dawei Li
<dawei.li@...ngroup.cn>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, Rasmus Villemoes
<linux@...musvillemoes.dk>, Yury Norov <yury.norov@...il.com>, lkml
<linux-kernel@...r.kernel.org>
Subject: Re: Boot failure with kernel BUG at mm/usercopy.c on next-20240325
On Mon, 25 Mar 2024 13:50:17 +0100 Borislav Petkov <bp@...en8.de> wrote:
> Adding more people from that
>
> 328c801335d5 ("cpumask: create dedicated kmem cache for cpumask var")
>
> in linux-next.
>
> On Mon, Mar 25, 2024 at 01:40:20PM +0100, V, Narasimhan wrote:
> > [AMD Official Use Only - General]
> >
> > Hi,
> > There is a boot failure as below.
> > On bisecting, the bad commit is found to be 328c801335d5f7edf2a3c9c331ddf8978f21e2a7.
> > Boots fine if we revert the above bad commit.
>
> Narasimhan,
>
> please send your .config and reproduction instructions. I'm guessing
> you're simply booting it, right?
>
> Leaving in the rest for the newly CCed people.
Thanks, I'll just drop the patch. It didn't receive a very favorable
review reception anyway.
Powered by blists - more mailing lists