[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4eced2d-8e64-f265-577a-878ed919f4cb@huawei.com>
Date: Thu, 13 Apr 2023 15:53:04 +0800
From: Chen Zhongjin <chenzhongjin@...wei.com>
To: David Laight <David.Laight@...LAB.COM>,
Dave Hansen <dave.hansen@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"akpm@...ux-foudation.org" <akpm@...ux-foudation.org>,
"ben-linux@...ff.org" <ben-linux@...ff.org>,
"wuchi.zero@...il.com" <wuchi.zero@...il.com>
Subject: Re: [PATCH 1/2] x86: profiling: remove lock functions hack for
!FRAME_POINTER
On 2023/4/12 18:01, David Laight wrote:
> From: Chen Zhongjin
>> Sent: 12 April 2023 08:02
> ...
>>> 4. !CONFIG_FRAME_POINTER is probably even more rare today than it was in
>>> 2006
>> No. !CONFIG_FRAME_POINTER is more common today because of UNWINDER_ORC.
>> And that is why the bug is triggered more frequently.
> CONFIG_FRAME_POINTER is pretty much required (on x86-64)
> for the user copy checks that are enabled in distro kernels.
Thanks for reminding.. I know little about distro kernels.
I though at least !CONFIG_FRAME_POINTER is more common than it was in 2006.
Not investigated but just because UNWINDER_ORC is defconfig and it
disables CONFIG_FRAME_POINTER.
Anyway, I kept the CONFIG_FRAME_POINTER not removed so it won't be affected.
Best,
Chen
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
Powered by blists - more mailing lists