From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sahil Gupta <s.gupta@arista.com>,
linux-trace-kernel@vger.kernel.org,
Kevin Mitchell <kevmitch@arista.com>,
Dmitry Safonov <dima@arista.com>
Subject: Re: ftrace: sorttable unable to sort ELF64 on 32-bit host
Date: Tue, 25 Mar 2025 07:58:36 -0400 [thread overview]
Message-ID: <2025032548-happily-saxophone-4079@gregkh> (raw)
In-Reply-To: <20250324150703.69665622@gandalf.local.home>
On Mon, Mar 24, 2025 at 03:07:03PM -0400, Steven Rostedt wrote:
> On Mon, 24 Mar 2025 11:52:33 -0700
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read:
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> >
> > </formletter>
>
> Hi Greg,
>
> This isn't a patch submission. It's more of a question if something should
> be backported because it happens to fix a long standing issue.
Sorry, that wasn't obvious to me.
> It appears that the ftrace mcount sorttable code was broken if you built a
> 64 bit kernel on a 32 bit machine. I'm guessing it was broken since 5.17?
> A recent update to this code coincidentally fixes that issue. That update
> landed in 6.14. The question is, is it fine to backport the changes that
> fix this? It may not be totally trivial to do so, but I could likely just
> backport the changes that address this issue.
It's up to the maintainer of the subsytem as to what they wish to see
happen. I will always defer to them as they are the ones that have to
deal with emails from users :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-25 11:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABEuK15=+Bo7xkBn5ufytVowt0j3fVEsdGVsryn1zH8KxfoCyQ@mail.gmail.com>
2025-03-24 17:36 ` ftrace: sorttable unable to sort ELF64 on 32-bit host Steven Rostedt
2025-03-24 18:39 ` Sahil Gupta
2025-03-24 18:52 ` Greg KH
2025-03-24 19:07 ` Steven Rostedt
2025-03-25 11:58 ` Greg KH [this message]
2025-03-25 12:15 ` Steven Rostedt
2025-03-25 17:52 ` Sahil Gupta
2025-03-25 18:02 ` Steven Rostedt
2025-03-25 18:10 ` Sahil Gupta
2025-03-25 18:19 ` Steven Rostedt
2025-03-25 18:23 ` Sahil Gupta
2025-03-26 0:06 ` [PATCH 6.1 6.6 6.12 6.13] scripts/sorttable: fix ELF64 mcount_loc address parsing when compiling on 32-bit Sahil Gupta
2025-03-26 0:23 ` Greg KH
2025-03-26 0:32 ` Steven Rostedt
2025-03-26 0:37 ` Steven Rostedt
2025-03-26 0:45 ` Greg KH
2025-03-26 0:47 ` Steven Rostedt
2025-03-26 1:07 ` Sahil Gupta
2025-05-03 10:24 ` Sahil Gupta
2025-03-26 2:23 ` Sasha Levin
2025-03-20 22:02 ftrace: sorttable unable to sort ELF64 on 32-bit host Sahil Gupta
2026-01-06 17:21 ` Steven Rostedt
2026-01-06 17:39 ` Sahil Gupta
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=2025032548-happily-saxophone-4079@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dima@arista.com \
--cc=kevmitch@arista.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=s.gupta@arista.com \
/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.