linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Sebastian Fricke <sebastian.fricke@collabora.com>,
	linux-trace-devel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	Torsten Duwe <duwe@suse.de>
Subject: Re: Corrupted function tracer in 5.17.0-rc1
Date: Mon, 4 Apr 2022 11:06:33 -0400	[thread overview]
Message-ID: <20220404110633.1b246d55@gandalf.local.home> (raw)
In-Reply-To: <YksG6LXUCwIZhK8k@FVFF77S0Q05N>

On Mon, 4 Apr 2022 15:55:36 +0100
Mark Rutland <mark.rutland@arm.com> wrote:

> From the title, this is v5.17-rc1, which is known broken due to the mcount sort
> issue that was subsequently fixed in commit:

Ah, yes. I was thinking of 5.18-rc1 (which has just been released)

> 
>   4ed308c445a1e3ab ("ftrace: Have architectures opt-in for mcount build time sorting")
> 
> Is it possible to try with the final v5.17? Or at least try with that patch
> cherry-picked?

Right, 5.17-rc1 is known broken. Please try the latest, 5.17 and let us
know if it is still an issue.

Thanks,

-- Steve

  reply	other threads:[~2022-04-04 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 12:52 Corrupted function tracer in 5.17.0-rc1 Sebastian Fricke
2022-04-04 14:26 ` Steven Rostedt
2022-04-04 14:55   ` Mark Rutland
2022-04-04 15:06     ` Steven Rostedt [this message]
2022-04-05 14:50       ` Sebastian Fricke

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=20220404110633.1b246d55@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=amit.kachhap@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=duwe@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sebastian.fricke@collabora.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 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).