From: Mark Brown <broonie@kernel.org>
To: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mete Durlu <meted@linux.ibm.com>
Subject: linux-next: manual merge of the s390 tree with the mm-nonmm-stable tree
Date: Wed, 14 Oct 2026 13:36:19 +0100 [thread overview]
Message-ID: <as93Q-hDP5cW6gaj@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
Hi all,
Today's linux-next merge of the s390 tree got a conflict in:
arch/s390/kernel/traps.c
between commit:
ed26d6fcf5631 ("s390: implement arch_do_panic")
from the mm-nonmm-stable tree and commit:
5cc8fe84f9117 ("s390/entry: Save lowcore on invalid kernel stack")
from the s390 tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc arch/s390/kernel/traps.c
index 115cb33732476,6b083b9584eb0..0000000000000
--- a/arch/s390/kernel/traps.c
+++ b/arch/s390/kernel/traps.c
@@@ -26,7 -26,7 +26,8 @@@
#include <linux/entry-common.h>
#include <linux/kmsan.h>
#include <linux/bug.h>
+#include <linux/panic.h>
+ #include <asm/pgmcheck-defs.h>
#include <asm/entry-percpu.h>
#include <asm/asm-extable.h>
#include <asm/irqflags.h>
@@@ -285,11 -290,12 +292,17 @@@ static void monitor_event_exception(str
}
}
+void arch_do_panic(void)
+{
+ disabled_wait();
+}
+
+ /*
+ * Content of the faulting CPU's lowcore, copied by stack_invalid().
+ */
+ struct lowcore stack_invalid_lowcore;
+ int stack_invalid_lowcore_used;
+
void kernel_stack_invalid(struct pt_regs *regs)
{
/*
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-10-14 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=as93Q-hDP5cW6gaj@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=meted@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
all inboxes | Powered by JetHome®