[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220405145020.55nopur6ccjyndnr@basti-XPS-13-9310>
Date: Tue, 5 Apr 2022 16:50:20 +0200
From: Sebastian Fricke <sebastian.fricke@...labora.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mark Rutland <mark.rutland@....com>,
linux-trace-devel@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Amit Daniel Kachhap <amit.kachhap@....com>,
Torsten Duwe <duwe@...e.de>
Subject: Re: Corrupted function tracer in 5.17.0-rc1
Hey Steven & Mark,
On 04.04.2022 11:06, Steven Rostedt wrote:
>On Mon, 4 Apr 2022 15:55:36 +0100
>Mark Rutland <mark.rutland@....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.
Using 5.18-rc1 it works well, thanks for the quick help.
>
>Thanks,
>
>-- Steve
Greetings,
Sebastian
Powered by blists - more mailing lists