From: Andrew Morton <akpm@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "V, Narasimhan" <Narasimhan.V@amd.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Aithal, Srikanth" <Srikanth.Aithal@amd.com>,
Dawei Li <dawei.li@shingroup.cn>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Yury Norov <yury.norov@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Boot failure with kernel BUG at mm/usercopy.c on next-20240325
Date: Mon, 25 Mar 2024 11:34:33 -0700 [thread overview]
Message-ID: <20240325113433.e04c2b508ac325630cd113c8@linux-foundation.org> (raw)
In-Reply-To: <20240325125017.GBZgFzCXVxeF50uGVE@fat_crate.local>
On Mon, 25 Mar 2024 13:50:17 +0100 Borislav Petkov <bp@alien8.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.
next prev parent reply other threads:[~2024-03-25 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:40 Boot failure with kernel BUG at mm/usercopy.c on next-20240325 V, Narasimhan
2024-03-25 12:50 ` Borislav Petkov
2024-03-25 18:34 ` Andrew Morton [this message]
2024-03-25 20:37 ` Borislav Petkov
2024-03-26 2:30 ` Feng Tang
2024-03-26 19:56 ` Andrew Morton
2024-03-25 15:28 ` Feng Tang
2024-03-25 17:48 ` V, Narasimhan
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 12:36 V, Narasimhan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240325113433.e04c2b508ac325630cd113c8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Narasimhan.V@amd.com \
--cc=Srikanth.Aithal@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dawei.li@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=yury.norov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.