From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Matthew Maurer <mmaurer@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: Do not export generated KASAN ODR symbols
Date: Thu, 6 Feb 2025 00:13:58 +0100 [thread overview]
Message-ID: <CANiq72m63F41Ee4cNx5w3SVhvYauzNRBo9ojZtSvGYcNhcs5ig@mail.gmail.com> (raw)
In-Reply-To: <CAGSQo02wJrawHfCJ7HTo+_o0wgk2zv+SefMmORoNcM5NNS7LqA@mail.gmail.com>
On Thu, Feb 6, 2025 at 12:12 AM Matthew Maurer <mmaurer@google.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
next prev parent reply other threads:[~2025-02-05 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 0:14 [PATCH] rust: Do not export generated KASAN ODR symbols Matthew Maurer
2025-01-22 8:38 ` Alice Ryhl
2025-01-22 9:11 ` Miguel Ojeda
2025-02-05 20:08 ` Matthew Maurer
2025-02-05 23:00 ` Miguel Ojeda
2025-02-05 23:03 ` Matthew Maurer
2025-02-05 23:08 ` Miguel Ojeda
2025-02-05 23:12 ` Matthew Maurer
2025-02-05 23:13 ` Miguel Ojeda [this message]
2025-02-06 23:04 ` 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=CANiq72m63F41Ee4cNx5w3SVhvYauzNRBo9ojZtSvGYcNhcs5ig@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmaurer@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).