From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] fdpic coredump stuff
Date: Fri, 7 Aug 2020 20:36:57 +0100 [thread overview]
Message-ID: <20200807193657.GV1236603@ZenIV.linux.org.uk> (raw)
Switches fdpic coredumps away from original aout dumping primitives
to the same kind of regset use as regular elf coredumps do.
The following changes since commit b4e9c9549f62329d2412f899635fddc5212b9cd4:
introduction of regset ->get() wrappers, switching ELF coredumps to those (2020-07-27 14:24:50 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.fdpic
for you to fetch changes up to 1697a322e28ba96d35953c5d824540d172546d36:
[elf-fdpic] switch coredump to regsets (2020-07-27 14:29:24 -0400)
----------------------------------------------------------------
Al Viro (7):
unexport linux/elfcore.h
take fdpic-related parts of elf_prstatus out
kill elf_fpxregs_t
[elf-fdpic] coredump: don't bother with cyclic list for per-thread objects
[elf-fdpic] move allocation of elf_thread_status into elf_dump_thread_status()
[elf-fdpic] use elf_dump_thread_status() for the dumper thread as well
[elf-fdpic] switch coredump to regsets
arch/ia64/include/asm/elf.h | 2 -
arch/powerpc/include/asm/elf.h | 2 -
arch/x86/include/asm/elf.h | 2 -
fs/binfmt_elf.c | 30 ------
fs/binfmt_elf_fdpic.c | 205 ++++++++++++++++++-----------------------
include/linux/elfcore-compat.h | 4 -
include/linux/elfcore.h | 66 +++++++++++--
include/uapi/linux/elfcore.h | 101 --------------------
scripts/headers_install.sh | 1 -
usr/include/Makefile | 1 -
10 files changed, 146 insertions(+), 268 deletions(-)
delete mode 100644 include/uapi/linux/elfcore.h
next reply other threads:[~2020-08-07 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 19:36 Al Viro [this message]
2020-08-07 20:39 ` [git pull] fdpic coredump stuff pr-tracker-bot
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=20200807193657.GV1236603@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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