[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <26149caf-af5f-01b0-1356-09dcf7c74cf0@linux.microsoft.com>
Date: Fri, 7 Apr 2023 22:41:40 -0500
From: "Madhavan T. Venkataraman" <madvenka@...ux.microsoft.com>
To: Dylan Hatch <dylanbhatch@...gle.com>, misono.tomohiro@...itsu.com
Cc: broonie@...nel.org, catalin.marinas@....com,
chenzhongjin@...wei.com, jamorris@...ux.microsoft.com,
jpoimboe@...hat.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, live-patching@...r.kernel.org,
mark.rutland@....com, nobuta.keiya@...itsu.com,
peterz@...radead.org, pmladek@...e.com, sjitindarsingh@...il.com,
will@...nel.org
Subject: Re: [RFC PATCH v3 00/22] arm64: livepatch: Use ORC for dynamic frame
pointer validation
Sorry for the delay. Someone else also pointed out the same thing. I just have not
had the chance to look at this. I plan to soon.
Thanks.
Madhavan
On 4/3/23 17:26, Dylan Hatch wrote:
>> Then, I noticed that invoke_syscall generates instructions to add random offset
>> in sp when RANDOMIZE_KSTACK_OFFSET=y, which is true in the above case.
>
> I'm also seeing this behavior when compiling with
> RANDOMIZE_KSTACK_OFFSET=y. I wonder if a special hint type
> could/should be added to allow for skipping the reliability check for
> stack frames with this randomized offset? Forgive me if this is a
> naive suggestion.
>
> Thanks,
> Dylan
Powered by blists - more mailing lists