mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Miguel Ojeda <ojeda@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>
Cc: linux-kbuild@vger.kernel.org, "Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Sergio González Collado" <sergio.collado@gmail.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev
Subject: Re: `KSYM_NAME_LEN` strikes again
Date: Sun, 30 Nov 2025 20:56:29 -0800	[thread overview]
Message-ID: <470357d7-5958-4470-a718-25b9c7660565@nvidia.com> (raw)
In-Reply-To: <20251201021659.1729308-1-ojeda@kernel.org>

On 11/30/25 6:16 PM, Miguel Ojeda wrote:
> Hi all,
> 
> In some Rust configs with -Os and doctests enabled, we are hitting
> KSYM_NAME_LEN again:
...
> Other options:
> 
>    - Conditionally doing it only for those builds that need it, to avoid
>      penalizing other builds (including normal Rust builds).
> 
>    - Building the Rust side with -O2 for now, or at least tweaking some
>      of the inlining behavior under -Os.
> 
>    - Not supporting Rust for `CC_OPTIMIZE_FOR_SIZE` for now (e.g. under
>      `BROKEN`).
> 
>    - Stop all this and go with a hashing approach like Willy/Linus
>      discussed back then:
> 
>          https://lore.kernel.org/rust-for-linux/CAHk-=whzXv=Fu7dQshSTyd9H1-JS5=gyKwW-GMNGccAKs4Mwpg@mail.gmail.com/
  
I'm impressed that you listed this last one, because it seems like a
somewhat extensive project!

But if it's actually an option, it seems like a very nice one:
a durable and long-lasting fix.

Maybe we would also get demangled backtraces at runtime as a side
effect, which would remove another minor bit of unhappiness too.
  

thanks,
-- 
John Hubbard


  reply	other threads:[~2025-12-01  4:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  2:16 Miguel Ojeda
2025-12-01  4:56 ` John Hubbard [this message]
2025-12-01 16:30   ` Miguel Ojeda
2025-12-01  9:15 ` david laight
2025-12-01 16:32   ` Miguel Ojeda

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=470357d7-5958-4470-a718-25b9c7660565@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=ojeda@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sergio.collado@gmail.com \
    --cc=tmgross@umich.edu \
    /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

all inboxes | Powered by JetHome®