From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] vfs.git elfcore pile
Date: Mon, 12 Dec 2022 00:24:44 +0000 [thread overview]
Message-ID: <Y5Z0zPBjWtXTWxLF@ZenIV> (raw)
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-elfcore
for you to fetch changes up to 38ba2f11d9ce0e7c9444e57cb1bb418d1979534b:
[elf] get rid of get_note_info_size() (2022-11-24 23:26:04 -0500)
Trivial conflicts with Kees' binfmt_elf branch; some of the whitespace
changes in his branch are in the code eliminated in this one.
----------------------------------------------------------------
Unification of regset and non-regset sides of ELF coredump
handling. Collecting per-thread register values is the
only thing that needs to be ifdefed there...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (10):
kill signal_pt_regs()
kill coredump_params->regs
kill extern of vsyscall32_sysctl
[elf][regset] clean fill_note_info() a bit
[elf][regset] simplify thread list handling in fill_note_info()
elf_core_copy_task_regs(): task_pt_regs is defined everywhere
[elf][non-regset] uninline elf_core_copy_task_fpregs() (and lose pt_regs argument)
[elf][non-regset] use elf_core_copy_task_regs() for dumper as well
[elf] unify regset and non-regset cases
[elf] get rid of get_note_info_size()
arch/alpha/include/asm/elf.h | 6 -
arch/alpha/include/asm/ptrace.h | 1 -
arch/alpha/kernel/process.c | 8 +-
arch/csky/kernel/process.c | 4 +-
arch/m68k/kernel/process.c | 4 +-
arch/microblaze/kernel/process.c | 2 +-
arch/um/kernel/process.c | 3 +-
arch/x86/include/asm/elf.h | 1 -
arch/x86/um/asm/elf.h | 4 -
fs/binfmt_elf.c | 271 ++++++++-------------------------------
fs/coredump.c | 1 -
include/linux/coredump.h | 1 -
include/linux/elfcore.h | 13 +-
include/linux/ptrace.h | 9 --
kernel/signal.c | 2 +-
15 files changed, 64 insertions(+), 266 deletions(-)
next reply other threads:[~2022-12-12 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 0:24 Al Viro [this message]
2022-12-13 3:49 ` 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=Y5Z0zPBjWtXTWxLF@ZenIV \
--to=viro@zeniv.linux.org.uk \
--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
all inboxes | Powered by JetHome®