public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: fuqiang wang <fuqiang.wang@easystack.cn>
To: Baoquan He <bhe@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86/kexec: fix potential cmem->ranges out of bounds
Date: Mon, 25 Dec 2023 21:44:02 +0800	[thread overview]
Message-ID: <a65e7a06-bc91-4c82-9a65-6066f9f64409@easystack.cn> (raw)
In-Reply-To: <ZYe3iN816iiKDwIu@MiWiFi-R3L-srv>

在 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 ?

Thanks a lot again
fuqiang

  reply	other threads:[~2023-12-25 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 12:18 [PATCH v3] x86/kexec: fix potential cmem->ranges out of bounds fuqiang wang
2023-12-22 13:29 ` Baoquan He
2023-12-24  4:46   ` Baoquan He
2023-12-25 13:44     ` fuqiang wang [this message]
2023-12-25 23:31       ` Baoquan He

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=a65e7a06-bc91-4c82-9a65-6066f9f64409@easystack.cn \
    --to=fuqiang.wang@easystack.cn \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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