From: Josh Poimboeuf <jpoimboe@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Chen Zhongjin <chenzhongjin@huawei.com>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH 0/2] x86/unwind/orc: Fix unwinding from kprobe on PUSH/POP instruction
Date: Fri, 10 Feb 2023 14:42:00 -0800 [thread overview]
Message-ID: <cover.1676068346.git.jpoimboe@kernel.org> (raw)
Josh Poimboeuf (2):
x86/unwind/orc: Add 'signal' field to ORC metadata
x86/entry: Fix unwinding from kprobe on PUSH/POP instruction
arch/x86/entry/entry_64.S | 9 ++++++++-
arch/x86/include/asm/orc_types.h | 4 +++-
arch/x86/include/asm/unwind_hints.h | 10 +++++-----
arch/x86/kernel/unwind_orc.c | 5 ++---
include/linux/objtool.h | 11 +++++++----
tools/arch/x86/include/asm/orc_types.h | 4 +++-
tools/include/linux/objtool.h | 11 +++++++----
tools/objtool/orc_dump.c | 4 ++--
8 files changed, 37 insertions(+), 21 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-10 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 22:42 Josh Poimboeuf [this message]
2023-02-10 22:42 ` [PATCH 1/2] x86/unwind/orc: Add 'signal' field to ORC metadata Josh Poimboeuf
2023-02-11 11:52 ` [tip: objtool/core] " tip-bot2 for Josh Poimboeuf
2023-02-10 22:42 ` [PATCH 2/2] x86/entry: Fix unwinding from kprobe on PUSH/POP instruction Josh Poimboeuf
2023-02-11 11:52 ` [tip: objtool/core] " tip-bot2 for Josh Poimboeuf
2023-02-13 14:43 ` [PATCH 2/2] " Masami Hiramatsu
2023-02-14 11:35 ` Peter Zijlstra
2023-02-14 17:05 ` Josh Poimboeuf
2023-02-15 10:25 ` Peter Zijlstra
2023-02-15 23:16 ` Josh Poimboeuf
2023-02-16 10:46 ` Peter Zijlstra
2023-02-16 11:30 ` Peter Zijlstra
2023-02-16 14:35 ` Masami Hiramatsu
2023-02-16 16:58 ` Josh Poimboeuf
2023-02-16 11:58 ` Peter Zijlstra
2023-02-16 16:06 ` Josh Poimboeuf
2023-02-17 12:44 ` Peter Zijlstra
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.1676068346.git.jpoimboe@kernel.org \
--to=jpoimboe@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=chenzhongjin@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.