[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYBM9MG1rjCDPykI@MiWiFi-R3L-srv>
Date: Mon, 18 Dec 2023 21:45:24 +0800
From: Baoquan He <bhe@...hat.com>
To: Yuntao Wang <ytcoode@...il.com>
Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, x86@...nel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Vivek Goyal <vgoyal@...hat.com>,
Dave Young <dyoung@...hat.com>,
Hari Bathini <hbathini@...ux.ibm.com>,
Sean Christopherson <seanjc@...gle.com>,
Takashi Iwai <tiwai@...e.de>
Subject: Re: [PATCH 0/2] crash: fix potential cmem->ranges array overflow
Hi Yuntao,
On 12/18/23 at 04:19pm, Yuntao Wang wrote:
> This series tries to fix the potential cmem->ranges array overflow.
This series looks good to me. While you'd better talk to fuqiang to ask
if he wants to post these or wants to give up. He posted patch to raise
the potention issue and I suggested him to do these during the
discussion. Without consulting him for opinion to take over a discussing
work, it's not suggested, I would say.
https://lore.kernel.org/all/ZXrY7QbXAlxydsSC@MiWiFi-R3L-srv/T/#u
>
> Yuntao Wang (2):
> x86/crash: fix potential cmem->ranges array overflow
> crash_core: fix out-of-bounds access check in
> crash_exclude_mem_range()
>
> arch/x86/kernel/crash.c | 9 +++++----
> kernel/crash_core.c | 2 +-
> 2 files changed, 6 insertions(+), 5 deletions(-)
>
> --
> 2.43.0
>
Powered by blists - more mailing lists