All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bradley Morgan <include@grrlz.net>
To: akpm@linux-foundation.org
Cc: pavel@kernel.org, tony.luck@intel.com, baoquan.he@linux.dev,
	rafael@kernel.org, kees@kernel.org, linux-pm@vger.kernel.org,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	rppt@kernel.org, Bradley Morgan <include@grrlz.net>,
	pasha.tatashin@soleen.com, pratyush@kernel.org, lenb@kernel.org
Subject: [PATCH v2 2/3] kexec: log the task that initiated the kexec reboot
Date: Tue, 21 Jul 2026 16:13:57 +0100	[thread overview]
Message-ID: <20260721151358.4185467-3-include@grrlz.net> (raw)
In-Reply-To: <20260721151358.4185467-1-include@grrlz.net>

The reboot syscall now logs the initiating task for the restart, halt
and power off commands at the point where they can no longer fail.
The kexec command could not be handled there: kernel_kexec() has
several failure points and returns to a running system when any of
them fires, which would leave a stale "initiated by" line in the log
with no transition behind it.

Call reboot_log_initiator() from kernel_kexec() once the shutdown
of the current kernel is committed, right before the existing
"Starting new kernel" line:

  reboot: initiated by kexec[713]
  kexec_core: Starting new kernel

The preserve_context path is left alone since it returns to the
running kernel instead of tearing it down.

Signed-off-by: Bradley Morgan <include@grrlz.net>
---
 kernel/kexec_core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
index dc770b9a6d05..23b7fe36e64e 100644
--- a/kernel/kexec_core.c
+++ b/kernel/kexec_core.c
@@ -1200,6 +1200,7 @@ int kernel_kexec(void)
 		 * CPU hotplug again; so re-enable it here.
 		 */
 		cpu_hotplug_enable();
+		reboot_log_initiator();
 		pr_notice("Starting new kernel\n");
 		machine_shutdown();
 	}
-- 
2.50.1



WARNING: multiple messages have this Message-ID (diff)
From: Bradley Morgan <include@grrlz.net>
To: akpm@linux-foundation.org
Cc: baoquan.he@linux.dev, rppt@kernel.org, pasha.tatashin@soleen.com,
	pratyush@kernel.org, rafael@kernel.org, lenb@kernel.org,
	pavel@kernel.org, kees@kernel.org, tony.luck@intel.com,
	gpiccoli@igalia.com, linux-kernel@vger.kernel.org,
	kexec@lists.infradead.org, linux-pm@vger.kernel.org,
	Bradley Morgan <include@grrlz.net>
Subject: [PATCH v2 2/3] kexec: log the task that initiated the kexec reboot
Date: Tue, 21 Jul 2026 16:13:57 +0100	[thread overview]
Message-ID: <20260721151358.4185467-3-include@grrlz.net> (raw)
In-Reply-To: <20260721151358.4185467-1-include@grrlz.net>

The reboot syscall now logs the initiating task for the restart, halt
and power off commands at the point where they can no longer fail.
The kexec command could not be handled there: kernel_kexec() has
several failure points and returns to a running system when any of
them fires, which would leave a stale "initiated by" line in the log
with no transition behind it.

Call reboot_log_initiator() from kernel_kexec() once the shutdown
of the current kernel is committed, right before the existing
"Starting new kernel" line:

  reboot: initiated by kexec[713]
  kexec_core: Starting new kernel

The preserve_context path is left alone since it returns to the
running kernel instead of tearing it down.

Signed-off-by: Bradley Morgan <include@grrlz.net>
---
 kernel/kexec_core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
index dc770b9a6d05..23b7fe36e64e 100644
--- a/kernel/kexec_core.c
+++ b/kernel/kexec_core.c
@@ -1200,6 +1200,7 @@ int kernel_kexec(void)
 		 * CPU hotplug again; so re-enable it here.
 		 */
 		cpu_hotplug_enable();
+		reboot_log_initiator();
 		pr_notice("Starting new kernel\n");
 		machine_shutdown();
 	}
-- 
2.50.1


  parent reply	other threads:[~2026-07-21 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 15:13 [PATCH v2 0/3] reboot: log the task that initiated Bradley Morgan
2026-07-21 15:13 ` Bradley Morgan
2026-07-21 15:13 ` [PATCH v2 1/3] reboot: log the task that initiated the reboot Bradley Morgan
2026-07-21 15:13   ` Bradley Morgan
2026-07-21 15:13 ` Bradley Morgan [this message]
2026-07-21 15:13   ` [PATCH v2 2/3] kexec: log the task that initiated the kexec reboot Bradley Morgan
2026-07-21 15:13 ` [PATCH v2 3/3] PM: hibernate: log the task that initiated the power down Bradley Morgan
2026-07-21 15:13   ` Bradley Morgan

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=20260721151358.4185467-3-include@grrlz.net \
    --to=include@grrlz.net \
    --cc=akpm@linux-foundation.org \
    --cc=baoquan.he@linux.dev \
    --cc=kees@kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pavel@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=rafael@kernel.org \
    --cc=rppt@kernel.org \
    --cc=tony.luck@intel.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.