[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZYoQ5ej3uDKt5rmw@MiWiFi-R3L-srv>
Date: Tue, 26 Dec 2023 07:31:49 +0800
From: Baoquan He <bhe@...hat.com>
To: fuqiang wang <fuqiang.wang@...ystack.cn>, akpm@...ux-foundation.org
Cc: Vivek Goyal <vgoyal@...hat.com>, Dave Young <dyoung@...hat.com>,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] x86/kexec: fix potential cmem->ranges out of bounds
On 12/25/23 at 09:44pm, fuqiang wang wrote:
> 在 2023/12/24 12:46, Baoquan He 写道:
>
> > Rethink about this, seems above code comment is fine to be kept, and the
> > same feeling about the elfheader region split from crashk_res. So, other
> > than the patch log concerns, this patch looks good to me. Let's see if
> > other people has concern about the newly added comments.
> >
>
> Hi Baoquan
>
> Thank you very much for your suggestions in the patch log and code comments. I
> have learned a lot and I will gradually improve.
>
> I found the following patch in linux-next:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=666ef13f2870c43ba8a402ec8a3cedf6eb6c6f5a
>
> I'm sorry, It's my mistake. Do you think it is still necessary to merge this
> patch based on that ?
That patch need be withdrew because that is not expected according to
our discussion.
Hi Andrew,
Could you withdraw the patch fuqiang mentioned?
x86/crash: fix potential cmem->ranges array overflow
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=666ef13f2870c43ba8a402ec8a3cedf6eb6c6f5a
Thanks
Powered by blists - more mailing lists