From: Sohil Mehta <sohil.mehta@intel.com>
To: "Xin Li (Intel)" <xin@zytor.com>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<shuah@kernel.org>, <andrew.cooper3@citrix.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v6 0/2] x86/fred: Prevent immediate repeat of single step trap on return from SIGTRAP handler
Date: Mon, 9 Jun 2025 09:34:27 -0700 [thread overview]
Message-ID: <a31448d0-bc0a-4bc9-8edd-1986ff5244bc@intel.com> (raw)
In-Reply-To: <20250609084054.2083189-1-xin@zytor.com>
On 6/9/2025 1:40 AM, Xin Li (Intel) wrote:
>
> Xin Li (Intel) (2):
> x86/fred/signal: Prevent immediate repeat of single step trap on
> return from SIGTRAP handler
> selftests/x86: Add a test to detect infinite SIGTRAP handler loop
>
I see that Dave just applied the patches. Sending this out anyway since
I was done reviewing them.
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> arch/x86/include/asm/sighandling.h | 22 +++++
> arch/x86/kernel/signal_32.c | 4 +
> arch/x86/kernel/signal_64.c | 4 +
> tools/testing/selftests/x86/Makefile | 2 +-
> tools/testing/selftests/x86/sigtrap_loop.c | 101 +++++++++++++++++++++
> 5 files changed, 132 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/x86/sigtrap_loop.c
>
>
> base-commit: dd2922dcfaa3296846265e113309e5f7f138839f
prev parent reply other threads:[~2025-06-09 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 8:40 Xin Li (Intel)
2025-06-09 8:40 ` [PATCH v6 1/2] x86/fred/signal: " Xin Li (Intel)
2025-06-09 8:40 ` [PATCH v6 2/2] selftests/x86: Add a test to detect infinite SIGTRAP handler loop Xin Li (Intel)
2025-06-09 16:34 ` Sohil Mehta [this message]
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=a31448d0-bc0a-4bc9-8edd-1986ff5244bc@intel.com \
--to=sohil.mehta@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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®