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 0/3] reboot: log the task that initiated
Date: Tue, 21 Jul 2026 16:13:55 +0100 [thread overview]
Message-ID: <20260721151358.4185467-1-include@grrlz.net> (raw)
When a machine reboots, powers off, kexecs or hibernates, the kernel
log records what happened but not who asked for it. This series logs
the comm and pid of the initiating task once the transition is
committed:
reboot: initiated by systemd-shutdow[1]
reboot: Restarting system
Patch 1 covers the restart, halt and power off commands of the
reboot syscall. Patches 2 and 3 give kexec and the hibernation power
down the same treatment at their own points of no return, as
suggested in the v1 review [1]. The kexec and PM maintainers are on
cc for their input on those two.
v1 -> v2:
- Reworded the justification in patch 1: dropped the fleet operator
claim and spelled out the concrete gap in userspace logging
- New patch 2: log the initiator for kexec reboots
- New patch 3: log the initiator for the hibernation power down
- Added the kexec and PM maintainers and lists to cc
[1] https://lore.kernel.org/all/20260719160938.3692-1-include@grrlz.net/
Bradley Morgan (3):
reboot: log the task that initiated the reboot
kexec: log the task that initiated the kexec reboot
PM: hibernate: log the task that initiated the power down
include/linux/reboot.h | 1 +
kernel/kexec_core.c | 1 +
kernel/power/hibernate.c | 2 ++
kernel/reboot.c | 16 ++++++++++++++++
4 files changed, 20 insertions(+)
--
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 0/3] reboot: log the task that initiated
Date: Tue, 21 Jul 2026 16:13:55 +0100 [thread overview]
Message-ID: <20260721151358.4185467-1-include@grrlz.net> (raw)
When a machine reboots, powers off, kexecs or hibernates, the kernel
log records what happened but not who asked for it. This series logs
the comm and pid of the initiating task once the transition is
committed:
reboot: initiated by systemd-shutdow[1]
reboot: Restarting system
Patch 1 covers the restart, halt and power off commands of the
reboot syscall. Patches 2 and 3 give kexec and the hibernation power
down the same treatment at their own points of no return, as
suggested in the v1 review [1]. The kexec and PM maintainers are on
cc for their input on those two.
v1 -> v2:
- Reworded the justification in patch 1: dropped the fleet operator
claim and spelled out the concrete gap in userspace logging
- New patch 2: log the initiator for kexec reboots
- New patch 3: log the initiator for the hibernation power down
- Added the kexec and PM maintainers and lists to cc
[1] https://lore.kernel.org/all/20260719160938.3692-1-include@grrlz.net/
Bradley Morgan (3):
reboot: log the task that initiated the reboot
kexec: log the task that initiated the kexec reboot
PM: hibernate: log the task that initiated the power down
include/linux/reboot.h | 1 +
kernel/kexec_core.c | 1 +
kernel/power/hibernate.c | 2 ++
kernel/reboot.c | 16 ++++++++++++++++
4 files changed, 20 insertions(+)
--
2.50.1
next 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 Bradley Morgan [this message]
2026-07-21 15:13 ` [PATCH v2 0/3] reboot: log the task that initiated 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 ` [PATCH v2 2/3] kexec: log the task that initiated the kexec reboot Bradley Morgan
2026-07-21 15:13 ` 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-1-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.