[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72m63F41Ee4cNx5w3SVhvYauzNRBo9ojZtSvGYcNhcs5ig@mail.gmail.com>
Date: Thu, 6 Feb 2025 00:13:58 +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>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: Do not export generated KASAN ODR symbols
On Thu, Feb 6, 2025 at 12:12 AM Matthew Maurer <mmaurer@...gle.com> wrote:
>
> Correct, I don't believe it needs to be backported. `gendwarfksyms` is
> the only in-tree tool I am aware of breaking on this. It is possible
> someone else is dumping DWARF for all exported symbols, but I don't
> know of anyone specific other than Android for kernel ABI monitoring,
> who already has this patch in-tree, and does that monitoring on
> non-ASAN builds.
Then I guess we could add a Fixes tag to one of those recent commits
(i.e. where `gendwarfksyms` is added), so that it doesn't trigger the
stable team into a backport.
But it is not a big deal -- if no recent commit really fits, I can
still apply it into `rust-fixes` without a tag.
Cheers,
Miguel
Powered by blists - more mailing lists