linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Wenyu Liu <liuwenyu7@huawei.com>,
	ebiederm@xmission.com, dmitry.kasatkin@gmail.com,
	paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-integrity@vger.kernel.org
Cc: akpm@linux-foundation.org, vschneid@redhat.com,
	pmenzel@molgen.mpg.de, bhe@redhat.com, louhongxiang@huawei.com
Subject: Re: [PATCH v2 RESEND] kexec_lock: Replace kexec_mutex() by kexec_lock() in two comments
Date: Mon, 07 Aug 2023 10:12:16 -0400	[thread overview]
Message-ID: <53b8559db650886f013d5e91704ce8f4df77d815.camel@linux.ibm.com> (raw)
In-Reply-To: <20230807025206.3682381-1-liuwenyu7@huawei.com>

On Mon, 2023-08-07 at 10:52 +0800, Wenyu Liu wrote:
> kexec_mutex is replaced by an atomic variable
> in 05c6257433b (panic, kexec: make __crash_kexec() NMI safe).
> 
> But there are still two comments that referenced kexec_mutex,
> replace them by kexec_lock.
> 
> Signed-off-by: Wenyu Liu <liuwenyu7@huawei.com>
> Acked-by: Baoquan He <bhe@redhat.com>
> Acked-by: Paul Menzel <pmenzel@molgen.mpg.de>

Thank you. It's now queued 
https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/log/?h=next-integrity
.

--
thanks,

Mimi


      reply	other threads:[~2023-08-07 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  2:52 [PATCH v2 RESEND] kexec_lock: Replace kexec_mutex() by kexec_lock() in two comments Wenyu Liu
2023-08-07 14:12 ` Mimi Zohar [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=53b8559db650886f013d5e91704ce8f4df77d815.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=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-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=liuwenyu7@huawei.com \
    --cc=louhongxiang@huawei.com \
    --cc=paul@paul-moore.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=serge@hallyn.com \
    --cc=vschneid@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;
as well as URLs for NNTP newsgroup(s).