linux-kernel - Re: [PATCH v6] rust: support for shadow call stack sanitizer

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72kAS9yYS1EJvmwL9LXk_k3nVQ=ShE=k6_Baa7vuBNgnqA@mail.gmail.com>
Date: Tue, 27 Aug 2024 14:52:30 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Will Deacon <will@...nel.org>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Catalin Marinas <catalin.marinas@....com>, 
	Ard Biesheuvel <ardb@...nel.org>, Jamie Cunliffe <Jamie.Cunliffe@....com>, 
	Sami Tolvanen <samitolvanen@...gle.com>, Nathan Chancellor <nathan@...nel.org>, 
	Conor Dooley <conor@...nel.org>, Kees Cook <kees@...nel.org>, 
	Masahiro Yamada <masahiroy@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, Marc Zyngier <maz@...nel.org>, 
	Mark Rutland <mark.rutland@....com>, Mark Brown <broonie@...nel.org>, 
	Nick Desaulniers <ndesaulniers@...gle.com>, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>, 
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>, 
	Valentin Obst <kernel@...entinobst.de>, linux-kbuild@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v6] rust: support for shadow call stack sanitizer

On Tue, Aug 27, 2024 at 2:50 PM Will Deacon <will@...nel.org> wrote:
>
> For the arm64 parts:
>
> Acked-by: Will Deacon <will@...nel.org>
>
> In which tree do you plan to merge this?

If it goes in this cycle, and that is OK with you, then I think it
would be easiest to put it into Rust, since it depends on
`RUSTC_VERSION` which we will want to put there too since other things
will be placed on top too.

Thanks!

Cheers,
Miguel