From: Baoquan He <bhe@redhat.com>
To: Yuntao Wang <ytcoode@gmail.com>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Vivek Goyal <vgoyal@redhat.com>,
Dave Young <dyoung@redhat.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Sean Christopherson <seanjc@google.com>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 0/2] crash: fix potential cmem->ranges array overflow
Date: Mon, 18 Dec 2023 21:45:24 +0800 [thread overview]
Message-ID: <ZYBM9MG1rjCDPykI@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20231218081915.24120-1-ytcoode@gmail.com>
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
>
prev parent reply other threads:[~2023-12-18 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 8:19 [PATCH 0/2] crash: fix potential cmem->ranges array overflow Yuntao Wang
2023-12-18 8:19 ` [PATCH 1/2] x86/crash: " Yuntao Wang
2023-12-18 8:19 ` [PATCH 2/2] crash_core: fix out-of-bounds access check in crash_exclude_mem_range() Yuntao Wang
2023-12-18 17:29 ` Andrew Morton
2023-12-19 2:02 ` Yuntao Wang
2023-12-19 3:32 ` Baoquan He
2023-12-19 4:31 ` Yuntao Wang
2023-12-19 14:22 ` Baoquan He
2023-12-19 16:00 ` Yuntao Wang
2023-12-19 16:34 ` [PATCH] crash_core: optimize crash_exclude_mem_range() Yuntao Wang
2023-12-29 20:10 ` Andrew Morton
2023-12-30 10:28 ` Baoquan He
2024-01-02 15:20 ` Yuntao Wang
2023-12-18 13:45 ` Baoquan He [this message]
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=ZYBM9MG1rjCDPykI@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dyoung@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
--cc=ytcoode@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox