linux-kernel - Re: [PATCH] rust: sync: rcu: Mark Guard methods as inline

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

Message-ID: <Z9UeWyrcK1t27SQV@vaxr-BM6660-BM6360>
Date: Sat, 15 Mar 2025 14:29:47 +0800
From: I Hsin Cheng <richard120310@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Joel Fernandes <joelagnelf@...dia.com>, rostedt@...dmis.org,
	paulmck@...nel.org, frederic@...nel.org, neeraj.upadhyay@...nel.org,
	joel@...lfernandes.org, josh@...htriplett.org, boqun.feng@...il.com,
	urezki@...il.com, mathieu.desnoyers@...icios.com,
	jiangshanlai@...il.com, qiang.zhang1211@...il.com, ojeda@...nel.org,
	alex.gaynor@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
	benno.lossin@...ton.me, a.hindborg@...nel.org, aliceryhl@...gle.com,
	tmgross@...ch.edu, dakr@...nel.org, rcu@...r.kernel.org,
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
	skhan@...uxfoundation.org, jserv@...s.ncku.edu.tw
Subject: Re: [PATCH] rust: sync: rcu: Mark Guard methods as inline

On Fri, Mar 14, 2025 at 03:43:23PM +0100, Miguel Ojeda wrote:
> On Thu, Mar 13, 2025 at 5:30 AM Joel Fernandes <joelagnelf@...dia.com> wrote:
> >
> > Reviewed-by: Joel Fernandes <joelagnelf@...dia.com>
> >
> > If no objections, I can queue it for 6.16 but let me know if Rust maintainers
> > prefer to take it.
> 
> Thanks! That would be great -- FWIW:
> 
> Acked-by: Miguel Ojeda <ojeda@...nel.org>
> 
> By the way, should `read_lock()` be marked too? It just calls another
> (now `#[inline]` one).
> 
> Cheers,
> Miguel

Hi all,

Thanks for your kindly review and comments!

> By the way, should `read_lock()` be marked too? It just calls another
> (now `#[inline]` one).

I'll do it and fix the typo mentioned by Charalampos. I'll send v2 to
you ASAP. Thanks !

Best regards,
I Hsin Cheng