All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Carlos Llamas" <cmllamas@google.com>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Onur Özkan" <work@onurozkan.dev>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Benno Lossin" <lossin@kernel.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>, "Lyude Paul" <lyude@redhat.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Waiman Long" <longman@redhat.com>,
	"Will Deacon" <will@kernel.org>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	"Alvin Sun" <alvin.sun@linux.dev>
Subject: Re: [PATCH v4 0/5] Rate limited printing for Rust
Date: Fri, 31 Jul 2026 11:06:36 +0200	[thread overview]
Message-ID: <2026073148-cushy-mocha-2ecf@gregkh> (raw)
In-Reply-To: <20260728-pr-ratelimited-v4-0-435f8d6e9605@google.com>

On Tue, Jul 28, 2026 at 09:32:50AM +0000, Alice Ryhl wrote:
> To avoid DoS on the kernel log, the Rust Binder driver is being switched
> to rate limited printing. But before we can do that, we must first
> implement rate limited printing for Rust. Thus, do that.
> 
> However, it turns out that before we can implement rate limited
> printing, we must first implement the ability declare a raw_spinlock_t
> in a global variable. Thus, do that too.
> 
> Based on top of char-misc-next plus this patch:
> https://lore.kernel.org/all/20260728061236.198267-1-aliceryhl@google.com/

Doesn't apply on my branch anymore, perhaps due to the other binder
patches I just accepted?

Ideally the rate-limit stuff could go through the rust tree, but that
would delay this a release cycle, so I don't mind taking this through
char-misc, if someone wants to rebase it yet-again :)

thanks,

greg k-h

  parent reply	other threads:[~2026-07-31  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  9:32 [PATCH v4 0/5] Rate limited printing for Rust Alice Ryhl
2026-07-28  9:32 ` [PATCH v4 1/5] rust: sync: move lockdep types to rust/kernel/sync/lockdep.rs Alice Ryhl
2026-07-28  9:32 ` [PATCH v4 2/5] rust: sync: add const constructor for raw_spinlock_t Alice Ryhl
2026-07-28  9:32 ` [PATCH v4 3/5] rust: add pr_*_ratelimit! macros for printing Alice Ryhl
2026-07-28  9:32 ` [PATCH v4 4/5] rust_binder: consolidate transaction failure prints Alice Ryhl
2026-07-28 17:10   ` Carlos Llamas
2026-07-28  9:32 ` [PATCH v4 5/5] rust_binder: use pr_*_ratelimited! for printing Alice Ryhl
2026-07-31  9:06 ` Greg Kroah-Hartman [this message]
2026-07-31 11:34   ` [PATCH v4 0/5] Rate limited printing for Rust Miguel Ojeda
2026-07-31 12:19     ` 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=2026073148-cushy-mocha-2ecf@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=alvin.sun@linux.dev \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=cmllamas@google.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=mingo@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=will@kernel.org \
    --cc=work@onurozkan.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.