lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <986c6fc8-b88c-347c-f599-283b34cf34b8@huawei.com>
Date: Wed, 30 Oct 2024 09:46:24 +0800
From: Jinjie Ruan <ruanjinjie@...wei.com>
To: "H. Peter Anvin" <hpa@...or.com>, <tglx@...utronix.de>,
	<mingo@...hat.com>, <bp@...en8.de>, <dave.hansen@...ux.intel.com>,
	<xin3.li@...el.com>, <krisman@...labora.com>, <x86@...nel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Remove unused _TIF_SINGLESTEP



On 2024/10/30 9:44, H. Peter Anvin wrote:
> On October 29, 2024 6:24:38 PM PDT, Jinjie Ruan <ruanjinjie@...wei.com> wrote:
>> Since following commit, _TIF_SINGLESTEP is not used by x86 anymore,
>> remove it.
>>
>> Fixes: 6342adcaa683 ("entry: Ensure trap after single-step on system call return")

This commit, sorry, the message is not so clear.

>> Signed-off-by: Jinjie Ruan <ruanjinjie@...wei.com>
>> ---
>> arch/x86/include/asm/thread_info.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h
>> index 12da7dfd5ef1..734db7221613 100644
>> --- a/arch/x86/include/asm/thread_info.h
>> +++ b/arch/x86/include/asm/thread_info.h
>> @@ -110,7 +110,6 @@ struct thread_info {
>> #define _TIF_NOTIFY_RESUME	(1 << TIF_NOTIFY_RESUME)
>> #define _TIF_SIGPENDING		(1 << TIF_SIGPENDING)
>> #define _TIF_NEED_RESCHED	(1 << TIF_NEED_RESCHED)
>> -#define _TIF_SINGLESTEP		(1 << TIF_SINGLESTEP)
>> #define _TIF_SSBD		(1 << TIF_SSBD)
>> #define _TIF_SPEC_IB		(1 << TIF_SPEC_IB)
>> #define _TIF_SPEC_L1D_FLUSH	(1 << TIF_SPEC_L1D_FLUSH)
> 
> "Following commit"?
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ