linux-kernel - Re: [PATCH v9 01/13] rust: hrtimer: introduce hrtimer support

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72kx31exTFohb3+9_=PGUq_JtqpCvG8=oQUc_gZB+De5og@mail.gmail.com>
Date: Mon, 24 Feb 2025 17:23:59 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Andreas Hindborg <a.hindborg@...nel.org>, Frederic Weisbecker <frederic@...nel.org>, 
	Anna-Maria Behnsen <anna-maria@...utronix.de>, Thomas Gleixner <tglx@...utronix.de>, 
	Danilo Krummrich <dakr@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <benno.lossin@...ton.me>, Alice Ryhl <aliceryhl@...gle.com>, 
	Trevor Gross <tmgross@...ch.edu>, Lyude Paul <lyude@...hat.com>, Guangbo Cui <2407018371@...com>, 
	Dirk Behme <dirk.behme@...il.com>, Daniel Almeida <daniel.almeida@...labora.com>, 
	Tamir Duberstein <tamird@...il.com>, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>
Subject: Re: [PATCH v9 01/13] rust: hrtimer: introduce hrtimer support

On Mon, Feb 24, 2025 at 4:46 PM Boqun Feng <boqun.feng@...il.com> wrote:
>
> Why do we need this new kconfig?

I suspect it is to provide flexibility (i.e. to avoid building
everything if there are no users of the abstraction) and/or to limit
the set of configs that may be affected by a breaking change on the C
side -- Andreas and I discussed it the other day. The description of
the issue has some lines, but perhaps the commit message could
clarify.

We have a similar one already, i.e. a "Rust-only" config, in
`CONFIG_RUST_FW_LOADER_ABSTRACTIONS`.

Since this one is default "y", it may still affect unrelated
subsystems that just enable `RUST=y`, though.

(I guess we could consider `select`ing from end users. But they cannot
be hidden symbols, because that limits the control too much (e.g.
someone may want to just build the abstraction), and in general they
may have dependencies, so it may not be a good idea.)

Cheers,
Miguel