From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] misc followups to regset work
Date: Mon, 14 Dec 2020 22:51:07 +0000 [thread overview]
Message-ID: <20201214225107.GD3579531@ZenIV.linux.org.uk> (raw)
Dead code removal, mostly; the only exception is a bit of cleanups
on itanic (getting rid of redundant stack unwinds - each access_uarea()
call does it and we call that 7 times in a row in ptrace_[sg]etregs(), *after*
having done it ourselves in the caller; location where the user registers
have been spilled won't change under us, and we can bloody well just call
access_elf_reg() directly, giving it the unw_frame_info we'd calculated for
our own purposes).
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git regset.followup
for you to fetch changes up to d4948d19d47f08f926db55f0fb8cb324e43f1c19:
c6x: kill ELF_CORE_COPY_FPREGS (2020-10-25 20:03:06 -0400)
----------------------------------------------------------------
Al Viro (5):
arm: kill dump_task_regs()
[ia64] missed cleanups from switch to regset coredumps
[ia64] ptrace_[sg]etregs(): use access_elf_reg() instead of access_uarea()
whack-a-mole: USE_ELF_CORE_DUMP
c6x: kill ELF_CORE_COPY_FPREGS
arch/arm/include/asm/elf.h | 4 ----
arch/arm/kernel/process.c | 9 --------
arch/c6x/include/asm/elf.h | 3 ---
arch/csky/include/asm/elf.h | 1 -
arch/hexagon/include/asm/elf.h | 1 -
arch/ia64/kernel/process.c | 2 +-
arch/ia64/kernel/ptrace.c | 51 ++++++++++++++++++++++--------------------
arch/nds32/include/asm/elf.h | 1 -
8 files changed, 28 insertions(+), 44 deletions(-)
next reply other threads:[~2020-12-14 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 22:51 Al Viro [this message]
2020-12-16 3:44 ` 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=20201214225107.GD3579531@ZenIV.linux.org.uk \
--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
Powered by JetHome