public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
	"Jamie Cunliffe" <Jamie.Cunliffe@arm.com>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Conor Dooley" <conor@kernel.org>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Marc Zyngier" <maz@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Valentin Obst" <kernel@valentinobst.de>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	rust-for-linux@vger.kernel.org, "Kees Cook" <kees@kernel.org>
Subject: Re: [PATCH v5] rust: support for shadow call stack sanitizer
Date: Fri, 23 Aug 2024 14:21:34 +0100	[thread overview]
Message-ID: <20240823132133.GC32156@willie-the-truck> (raw)
In-Reply-To: <CAH5fLgiCr3hOEX1yaqy66OMsbPTtEhA4FCmRiw20zY64vYKHPw@mail.gmail.com>

On Fri, Aug 23, 2024 at 03:09:40PM +0200, Alice Ryhl wrote:
> On Fri, Aug 23, 2024 at 2:57 PM Will Deacon <will@kernel.org> wrote:
> >
> > On Fri, Aug 23, 2024 at 02:38:20PM +0200, Alice Ryhl wrote:
> > > On Fri, Aug 23, 2024 at 2:24 PM Will Deacon <will@kernel.org> wrote:
> > > >
> > > > On Tue, Aug 20, 2024 at 05:13:58PM +0200, Alice Ryhl wrote:
> > > > > On Tue, Aug 20, 2024 at 4:35 PM Will Deacon <will@kernel.org> wrote:
> > > > > > On Tue, Aug 06, 2024 at 10:01:44AM +0000, Alice Ryhl wrote:
> > > > > > > diff --git a/init/Kconfig b/init/Kconfig
> > > > > > > index fe76c5d0a72e..d857f6f90885 100644
> > > > > > > --- a/init/Kconfig
> > > > > > > +++ b/init/Kconfig
> > > > > > > @@ -1909,7 +1909,7 @@ config RUST
> > > > > > >       depends on !MODVERSIONS
> > > > > > >       depends on !GCC_PLUGINS
> > > > > > >       depends on !RANDSTRUCT
> > > > > > > -     depends on !SHADOW_CALL_STACK
> > > > > > > +     depends on !SHADOW_CALL_STACK || RUSTC_VERSION >= 108000 && UNWIND_PATCH_PAC_INTO_SCS
> > > > > >
> > > > > > Sorry, I didn't spot this in v4, but since UNWIND_PATCH_PAC_INTO_SCS is
> > > > > > specific to arm64 and the only other architecture selecting
> > > > > > ARCH_SUPPORTS_SHADOW_CALL_STACK is riscv, I can't help but feel it would
> > > > > > be cleaner to move this logic into the arch code selecting HAVE_RUST.
> > > > > >
> > > > > > That is, it's up to the architecture to make sure that it has whatever
> > > > > > it needs for SCS to work with Rust if it claims to support Rust.
> > > > > >
> > > > > > What do you think?
> > > > >
> > > > > The `select RUST if ...` is going to get really complicated if we
> > > > > apply that rule in general. Having options here allows us to split
> > > > > them across several `depends on` clauses. I'm not sure it will even
> > > > > work, I had issues with cyclic Kconfig errors previously. I also don't
> > > > > think it's unreasonable for the architecture to say it supports both
> > > > > options when it really does support both; they are just mutually
> > > > > exclusive. I also think there is value in having all of the options
> > > > > that Rust doesn't work with in one place.
> > > >
> > > > I'm not sure I follow why this will get really complicated. Isn't it as
> > > > straightforward as the diff below, or did I miss something?
> > >
> > > Hmm. I tried this but I wasn't able to enable Rust with this setup.
> > > Even though the deps of RUSTC_SUPPORTS_ARM64 are ok, it doesn't seem
> > > to be enabled and I can't find it in menuconfig. I think we need to
> > > have a `select RUSTC_SUPPORTS_ARM64` somewhere.
> >
> > Sorry, yes, my diff was a little half-arsed:
> >
> > > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> > > > index a2f8ff354ca6..2f5702cb9dac 100644
> > > > --- a/arch/arm64/Kconfig
> > > > +++ b/arch/arm64/Kconfig
> > > > @@ -231,7 +231,7 @@ config ARM64
> > > >         select HAVE_FUNCTION_ARG_ACCESS_API
> > > >         select MMU_GATHER_RCU_TABLE_FREE
> > > >         select HAVE_RSEQ
> > > > -       select HAVE_RUST if CPU_LITTLE_ENDIAN
> > > > +       select HAVE_RUST if RUSTC_SUPPORTS_ARM64
> > > >         select HAVE_STACKPROTECTOR
> > > >         select HAVE_SYSCALL_TRACEPOINTS
> > > >         select HAVE_KPROBES
> > > > @@ -265,6 +265,11 @@ config ARM64
> > > >         help
> > > >           ARM 64-bit (AArch64) Linux support.
> > > >
> > > > +config RUSTC_SUPPORTS_ARM64
> > > > +       bool
> >
> > This line ^^^ should be 'def_bool y'.
> 
> Ah, I see, I guess I learned something today. It also seems to work if
> I add `default y`.
> 
> I can change it if you think this is better. I still think there's
> some value in having everything in one place, but it's not a big deal.
> Either way, it should be temporary for a few kernel releases as we'll
> eventually only support compiler versions where this works.

I do like moving the reference to UNWIND_PATCH_PAC_INTO_SCS into the
arch code, so if you could respin along these lines then that would be
great.

Thanks,

Will


  reply	other threads:[~2024-08-23 13:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 10:01 [PATCH v5] rust: support for shadow call stack sanitizer Alice Ryhl
2024-08-06 19:37 ` Kees Cook
2024-08-06 20:27 ` Sami Tolvanen
2024-08-20 14:35 ` Will Deacon
2024-08-20 15:13   ` Alice Ryhl
2024-08-23 12:24     ` Will Deacon
2024-08-23 12:38       ` Alice Ryhl
2024-08-23 12:57         ` Will Deacon
2024-08-23 13:09           ` Alice Ryhl
2024-08-23 13:21             ` Will Deacon [this message]
2024-08-27 11:36               ` Alice Ryhl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240823132133.GC32156@willie-the-truck \
    --to=will@kernel.org \
    --cc=Jamie.Cunliffe@arm.com \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=ardb@kernel.org \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor@kernel.org \
    --cc=gary@garyguo.net \
    --cc=kees@kernel.org \
    --cc=kernel@valentinobst.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masahiroy@kernel.org \
    --cc=maz@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=samitolvanen@google.com \
    --cc=wedsonaf@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox