From: Heiko Carstens <hca@linux.ibm.com>
To: Vasily Gorbik <gor@linux.ibm.com>
Cc: Mikhail Zaslonko <zaslonko@linux.ibm.com>,
Alexander Egorenkov <egorenar@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 1/2] s390/ipl: Fix NULL deref in kdump without re-IPL parm block
Date: Fri, 14 Aug 2026 16:41:34 +0200 [thread overview]
Message-ID: <20260814144134.135106Adf-hca@linux.ibm.com> (raw)
In-Reply-To: <p01-02.g87de83845c5f.ttjpfvt@ub.hpns>
On Thu, Aug 13, 2026 at 01:06:54PM +0200, Vasily Gorbik wrote:
> Some IPL types, like HMC FTP boot or QEMU direct kernel boot, might
> not provide an IPL parameter block. In this case, reipl_type_init()
> selects IPL_TYPE_UNKNOWN, and reipl_block_actual remains NULL.
>
> kdump passes the re-IPL parameter block to the dump kernel through
> os_info. Before commit 3b9678472bab ("s390/ipl: correct kdump reipl
> block checksum calculation"), the os_info entry was added only for
> IPL types which initialized reipl_block_actual. That commit moved the
> os_info update to machine_crash_shutdown(), making it unconditional. As
> a result, set_os_info_reipl_block() dereferences reipl_block_actual for
> IPL_TYPE_UNKNOWN. This may happen to work by chance when address zero
> contains readable lowcore data and the resulting empty os_info entry is
> ignored by the dump kernel.
>
> Skip the os_info update when no re-IPL parameter block is available.
> Kdump then collect the dump and reboot without setting re-IPL parameter
> block.
>
> Fixes: 3b9678472bab ("s390/ipl: correct kdump reipl block checksum calculation")
> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
> ---
> arch/s390/kernel/ipl.c | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
next prev parent reply other threads:[~2026-08-14 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:06 [PATCH 0/2] s390/ipl: Fix missing re-IPL parm blocks handling in dump paths Vasily Gorbik
2026-08-13 11:06 ` [PATCH 1/2] s390/ipl: Fix NULL deref in kdump without re-IPL parm block Vasily Gorbik
2026-08-13 11:19 ` sashiko-bot
2026-08-13 11:48 ` Vasily Gorbik
2026-08-14 14:41 ` Heiko Carstens [this message]
2026-08-13 11:06 ` [PATCH 2/2] s390/ipl: Fix NULL deref in dump_reipl " Vasily Gorbik
2026-08-13 11:25 ` sashiko-bot
2026-08-13 13:57 ` Mikhail Zaslonko
2026-08-17 17:37 ` [PATCH 0/2] s390/ipl: Fix missing re-IPL parm blocks handling in dump paths Vasily Gorbik
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=20260814144134.135106Adf-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=egorenar@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=zaslonko@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.