[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=q9z1O-OfSy9BHhzB+nAngQ+j79ps7OAEq+0Yzz4sHcw@mail.gmail.com>
Date: Tue, 11 Mar 2025 20:20:03 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Matthew Maurer <mmaurer@...gle.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org, Matthias Maennich <maennich@...gle.com>
Subject: Re: [PATCH] rust: Disallow BTF generation with Rust + LTO
On Thu, Jan 9, 2025 at 12:35 AM Matthew Maurer <mmaurer@...gle.com> wrote:
>
> The kernel cannot currently self-parse BTF containing Rust debug
> information. pahole uses the language of the CU to determine whether to
> filter out debug information when generating the BTF. When LTO is
> enabled, Rust code can cross CU boundaries, resulting in Rust debug
> information in CUs labeled as C. This results in a system which cannot
> parse its own BTF.
>
> Signed-off-by: Matthew Maurer <mmaurer@...gle.com>
Applied to `rust-fixes` -- thanks everyone!
Cc: stable@...r.kernel.org
Fixes: c1177979af9c ("btf, scripts: Exclude Rust CUs with pahole")
If someone disagrees with those tags, please let me know.
Cheers,
Miguel
Powered by blists - more mailing lists