From: Baoquan He <bhe@redhat.com>
To: "Wenyu Liu(D)" <liuwenyu7@huawei.com>
Cc: kexec@lists.infradead.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, ebiederm@xmission.com,
zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com
Subject: Re: [PATCH] kexec_lock:Fix comment for kexec_lock
Date: Mon, 24 Jul 2023 16:23:00 +0800 [thread overview]
Message-ID: <ZL405LGPVa6lOl5s@MiWiFi-R3L-srv> (raw)
In-Reply-To: <26ff12fe-347b-d908-0327-73cf3c83b00b@huawei.com>
On 07/24/23 at 11:45am, Wenyu Liu(D) wrote:
> kexec_mutex is replaced by an atomic variable in
> 56314b90fd43bd2444 (panic, kexec: make __crash_kexec() NMI safe).
You could use a distros kernel or customized kernel and made change
based on that. The commit id isn't correct. I pasted the right one
at below.
commit 05c6257433b ("panic, kexec: make __crash_kexec() NMI safe")
Other than this, this looks good. You can post a new one with my ack.
Acked-by: Baoquan He <bhe@redhat.com>
>
> Fix some comment that still using kexec_mutex.
>
> Signed-off-by: Wenyu Liu <liuwenyu7@huawei.com>
> ---
> kernel/kexec_file.c | 2 +-
> security/integrity/ima/ima_kexec.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
> index 881ba0d1714c..b5bbb2fe0668 100644
> --- a/kernel/kexec_file.c
> +++ b/kernel/kexec_file.c
> @@ -624,7 +624,7 @@ int kexec_locate_mem_hole(struct kexec_buf *kbuf)
> * kexec_add_buffer - place a buffer in a kexec segment
> * @kbuf: Buffer contents and memory parameters.
> *
> - * This function assumes that kexec_mutex is held.
> + * This function assumes that kexec_lock is held.
> * On successful return, @kbuf->mem will have the physical address of
> * the buffer in memory.
> *
> diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
> index 419dc405c831..ad133fe120db 100644
> --- a/security/integrity/ima/ima_kexec.c
> +++ b/security/integrity/ima/ima_kexec.c
> @@ -77,7 +77,7 @@ static int ima_dump_measurement_list(unsigned long *buffer_size, void **buffer,
> * Called during kexec_file_load so that IMA can add a segment to the kexec
> * image for the measurement list for the next kernel.
> *
> - * This function assumes that kexec_mutex is held.
> + * This function assumes that kexec_lock is held.
> */
> void ima_add_kexec_buffer(struct kimage *image)
> {
> --
> 2.33.0
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: "Wenyu Liu(D)" <liuwenyu7@huawei.com>
Cc: kexec@lists.infradead.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, ebiederm@xmission.com,
zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com
Subject: Re: [PATCH] kexec_lock:Fix comment for kexec_lock
Date: Mon, 24 Jul 2023 16:23:00 +0800 [thread overview]
Message-ID: <ZL405LGPVa6lOl5s@MiWiFi-R3L-srv> (raw)
In-Reply-To: <26ff12fe-347b-d908-0327-73cf3c83b00b@huawei.com>
On 07/24/23 at 11:45am, Wenyu Liu(D) wrote:
> kexec_mutex is replaced by an atomic variable in
> 56314b90fd43bd2444 (panic, kexec: make __crash_kexec() NMI safe).
You could use a distros kernel or customized kernel and made change
based on that. The commit id isn't correct. I pasted the right one
at below.
commit 05c6257433b ("panic, kexec: make __crash_kexec() NMI safe")
Other than this, this looks good. You can post a new one with my ack.
Acked-by: Baoquan He <bhe@redhat.com>
>
> Fix some comment that still using kexec_mutex.
>
> Signed-off-by: Wenyu Liu <liuwenyu7@huawei.com>
> ---
> kernel/kexec_file.c | 2 +-
> security/integrity/ima/ima_kexec.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
> index 881ba0d1714c..b5bbb2fe0668 100644
> --- a/kernel/kexec_file.c
> +++ b/kernel/kexec_file.c
> @@ -624,7 +624,7 @@ int kexec_locate_mem_hole(struct kexec_buf *kbuf)
> * kexec_add_buffer - place a buffer in a kexec segment
> * @kbuf: Buffer contents and memory parameters.
> *
> - * This function assumes that kexec_mutex is held.
> + * This function assumes that kexec_lock is held.
> * On successful return, @kbuf->mem will have the physical address of
> * the buffer in memory.
> *
> diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
> index 419dc405c831..ad133fe120db 100644
> --- a/security/integrity/ima/ima_kexec.c
> +++ b/security/integrity/ima/ima_kexec.c
> @@ -77,7 +77,7 @@ static int ima_dump_measurement_list(unsigned long *buffer_size, void **buffer,
> * Called during kexec_file_load so that IMA can add a segment to the kexec
> * image for the measurement list for the next kernel.
> *
> - * This function assumes that kexec_mutex is held.
> + * This function assumes that kexec_lock is held.
> */
> void ima_add_kexec_buffer(struct kimage *image)
> {
> --
> 2.33.0
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
next prev parent reply other threads:[~2023-07-24 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 3:45 [PATCH] kexec_lock:Fix comment for kexec_lock Wenyu Liu(D)
2023-07-24 3:45 ` Wenyu Liu(D)
2023-07-24 8:23 ` Baoquan He [this message]
2023-07-24 8:23 ` Baoquan He
2023-07-24 9:12 ` Wenyu Liu(D)
2023-07-24 9:12 ` Wenyu Liu(D)
2023-07-24 8:49 ` Paul Menzel
2023-07-24 8:49 ` Paul Menzel
2023-07-24 9:15 ` Wenyu Liu(D)
2023-07-24 9:15 ` Wenyu Liu(D)
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=ZL405LGPVa6lOl5s@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liuwenyu7@huawei.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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.