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-next>] [day] [month] [year] [list]
Date:   Mon, 3 Apr 2023 15:26:41 -0700
From:   Dylan Hatch <dylanbhatch@...gle.com>
To:     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,
        madvenka@...ux.microsoft.com, 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

> 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

Powered by Openwall GNU/*/Linux Powered by OpenVZ