summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-09-10 17:48:08 +0200
committerChristian Brauner <brauner@kernel.org>2026-10-05 13:11:49 +0200
commitc2fe52e23c12aef43c0522196c28f9e2721634ae (patch)
tree4d95cfdd64291d9982cb25dc2be2fcfef1aeef29 /tools/lib/python
parente07feeeb5b8db35ee02c2361e90a9d622d3050ee (diff)
downloadlinux-next-c2fe52e23c12aef43c0522196c28f9e2721634ae.tar.gz
linux-next-c2fe52e23c12aef43c0522196c28f9e2721634ae.zip
coredump: drop core_state->dumper
The core_state->dumper field isn't used anymore. Only its ->next pointer is. The current task is always the dumping thread and the ->task pointer is never read. Replace it with a plain pointer to the list of parked threads. Historically, core_state->dumper was used. Its ->task pointer was read. by fill_note_info() started at &core_state->dumper to ensure that the dumping thread came first in the ELF thread notes. That changed in commit 4b0e21d64253 ("[elf][regset] simplify thread list handling in fill_note_info()"). The first iteration was taken out of the loop. So it's been unused ever since. No functional changes. Suggested-by: NeilBrown <neilb@ownmail.net> Link: https://lore.kernel.org/178900159210.207413.8292125177519817528@noble.neil.brown.name Link: https://patch.msgid.link/20260910-work-coredump-unlock-self-v4-10-a5c1800dc930@kernel.org Reviewed-by: NeilBrown <neil@brown.name> Reviewed-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions