From: Markus Elfring <Markus.Elfring@web.de>
To: Tao Liu <ltao@redhat.com>,
linux-riscv@lists.infradead.org, kexec@lists.infradead.org,
linux-integrity@vger.kernel.org,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <pjw@kernel.org>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, Baoquan He <bhe@redhat.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Eric Snowberg <eric.snowberg@oracle.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Mimi Zohar <zohar@linux.ibm.com>,
Nutty Liu <nutty.liu@hotmail.com>,
Pratyush Yadav <pratyush@kernel.org>,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH v3] riscv: Fix a NULL pointer dereference in machine_kexec_prepare
Date: Wed, 1 Jul 2026 08:00:14 +0200 [thread overview]
Message-ID: <4b21e0d5-07d1-438b-a6ea-a2be596a3044@web.de> (raw)
In-Reply-To: <20260701025732.66330-2-ltao@redhat.com>
…
> Fix this by simply adding a check before copy.
a data copy attempt?
> Fixes: b7fb4d78a6ad ("RISC-V: use memcpy for kexec_file mode")
See also once more:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v7.2-rc1#n34
Would a summary phrase like “Prevent null pointer dereference in machine_kexec_prepare()”
be nicer?
Regards,
Markus
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-01 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 2:57 [PATCH v3] riscv: Fix a NULL pointer dereference in machine_kexec_prepare Tao Liu
2026-07-01 3:28 ` Nutty.Liu
2026-07-01 3:50 ` Jarkko Sakkinen
2026-07-01 4:58 ` Tao Liu
2026-07-01 10:34 ` Jarkko Sakkinen
2026-07-03 11:08 ` Tao Liu
2026-07-01 12:06 ` Pratyush Yadav
2026-07-03 10:59 ` Tao Liu
2026-07-01 6:00 ` Markus Elfring [this message]
2026-07-03 11:11 ` Tao Liu
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=4b21e0d5-07d1-438b-a6ea-a2be596a3044@web.de \
--to=markus.elfring@web.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=jarkko@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=ltao@redhat.com \
--cc=nutty.liu@hotmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=roberto.sassu@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox