From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH v4 0/9] kentry: A stable bugfix and a bunch of improvements
Date: Wed, 17 Mar 2021 11:12:39 -0700 [thread overview]
Message-ID: <cover.1616004689.git.luto@kernel.org> (raw)
I noticed a little bug in fast compat syscalls. I got a bit carried away
fixing it. This renames the irqentry stuff to kentry, improves (IMNSHO)
the API, and adds lots of debugging.
It also tweaks the unwinder wrt ret_from_fork and rewrites ret_from_fork
in C. I did this because the kentry work involved a small change to
ret_from_fork, and adjusting the asm is a mess. So C it is.
Changes from v3: Get rid of arm64 special cases
Changes from v1 and v2: Complete rewrite
Andy Lutomirski (9):
x86/dumpstack: Remove unnecessary range check fetching opcode bytes
x86/kthread,dumpstack: Set task_pt_regs->cs.RPL=3 for kernel threads
x86/entry: Convert ret_from_fork to C
kentry: Simplify the common syscall API
kentry: Remove enter_from/exit_to_user_mode()
entry: Make CONFIG_DEBUG_ENTRY available outside x86
kentry: Add debugging checks for proper kentry API usage
kentry: Check that syscall entries and syscall exits match
kentry: Verify kentry state in instrumentation_begin/end()
arch/x86/Kconfig.debug | 10 --
arch/x86/entry/common.c | 78 ++++++++++----
arch/x86/entry/entry_32.S | 51 ++-------
arch/x86/entry/entry_64.S | 33 ++----
arch/x86/include/asm/switch_to.h | 2 +-
arch/x86/kernel/dumpstack.c | 10 +-
arch/x86/kernel/process.c | 15 ++-
arch/x86/kernel/process_32.c | 2 +-
arch/x86/kernel/traps.c | 4 +-
arch/x86/kernel/unwind_orc.c | 2 +-
include/asm-generic/bug.h | 8 +-
include/linux/entry-common.h | 127 +++--------------------
include/linux/instrumentation.h | 25 ++++-
include/linux/sched.h | 4 +
init/init_task.c | 8 ++
kernel/entry/common.c | 173 ++++++++++++++++++++-----------
lib/Kconfig.debug | 11 ++
17 files changed, 267 insertions(+), 296 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-17 18:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 18:12 Andy Lutomirski [this message]
2021-03-17 18:12 ` [PATCH v4 1/9] x86/dumpstack: Remove unnecessary range check fetching opcode bytes Andy Lutomirski
2021-03-17 18:12 ` [PATCH v4 2/9] x86/kthread,dumpstack: Set task_pt_regs->cs.RPL=3 for kernel threads Andy Lutomirski
2021-03-18 0:36 ` Josh Poimboeuf
2021-03-17 18:12 ` [PATCH v4 3/9] x86/entry: Convert ret_from_fork to C Andy Lutomirski
2021-03-18 0:38 ` Josh Poimboeuf
2021-03-19 16:05 ` Thomas Gleixner
2021-03-17 18:12 ` [PATCH v4 4/9] kentry: Simplify the common syscall API Andy Lutomirski
2021-03-19 16:09 ` Thomas Gleixner
2021-03-19 18:07 ` Thomas Gleixner
2021-03-17 18:12 ` [PATCH v4 5/9] kentry: Remove enter_from/exit_to_user_mode() Andy Lutomirski
2021-03-19 18:08 ` Thomas Gleixner
2021-03-17 18:12 ` [PATCH v4 6/9] entry: Make CONFIG_DEBUG_ENTRY available outside x86 Andy Lutomirski
2021-03-17 18:12 ` [PATCH v4 7/9] kentry: Add debugging checks for proper kentry API usage Andy Lutomirski
2021-03-19 16:17 ` Thomas Gleixner
2021-03-19 18:16 ` Thomas Gleixner
2021-03-17 18:12 ` [PATCH v4 8/9] kentry: Check that syscall entries and syscall exits match Andy Lutomirski
2021-03-17 18:12 ` [PATCH v4 9/9] kentry: Verify kentry state in instrumentation_begin/end() Andy Lutomirski
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=cover.1616004689.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).