From: Vasily Gorbik <gor@linux.ibm.com>
To: Mikhail Zaslonko <zaslonko@linux.ibm.com>,
Alexander Egorenkov <egorenar@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>
Cc: linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/2] s390/ipl: Fix missing re-IPL parm blocks handling in dump paths
Date: Mon, 17 Aug 2026 19:37:16 +0200 [thread overview]
Message-ID: <ttjxcy4@ub.hpns> (raw)
In-Reply-To: <c00-02.ttjpfvt@ub.hpns>
On Thu, Aug 13, 2026 at 01:06:52PM +0200, Vasily Gorbik wrote:
> HMC FTP boot and QEMU direct kernel boot do not provide an IPL parameter
> block. This can lead to NULL pointer dereferences during kdump and
> stand-alone dump processing.
>
> Fix the kdump and stand-alone dump paths separately. kdump continues
> without a re-IPL parameter block, while the stand-alone dumper completes
> the dump and halts.
>
> Vasily Gorbik (2):
> s390/ipl: Fix NULL deref in kdump without re-IPL parm block
> s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block
>
> arch/s390/kernel/ipl.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
Applied
prev parent reply other threads:[~2026-08-17 17:37 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
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 ` Vasily Gorbik [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=ttjxcy4@ub.hpns \
--to=gor@linux.ibm.com \
--cc=egorenar@linux.ibm.com \
--cc=hca@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.