From: Steven Rostedt <rostedt@goodmis.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Rutland <mark.rutland@arm.com>,
Yinan Liu <yinan@linux.alibaba.com>,
Ard Biesheuvel <ardb@kernel.org>,
Kees Cook <keescook@chromium.org>,
Sachin Sant <sachinp@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ftrace: Have architectures opt-in for mcount build time sorting
Date: Fri, 28 Jan 2022 16:39:48 -0500 [thread overview]
Message-ID: <20220128163948.721c8b12@gandalf.local.home> (raw)
In-Reply-To: <YfRcC/ggq90jw7Uc@redhat.com>
On Fri, 28 Jan 2022 16:11:39 -0500
Joe Lawrence <joe.lawrence@redhat.com> wrote:
> The bisect finally landed on:
>
> 72b3942a173c387b27860ba1069636726e208777 is the first bad commit
> commit 72b3942a173c387b27860ba1069636726e208777
> Author: Yinan Liu <yinan@linux.alibaba.com>
> Date: Sun Dec 12 19:33:58 2021 +0800
>
> scripts: ftrace - move the sort-processing in ftrace_init
>
> and I can confirm that your updates today in "[for-linus][PATCH 00/10]
> tracing: Fixes for 5.17-rc1" fix or avoid the issue. I just wanted to
> add my report in case this adds any future complications for mcount
> build time sorting. Let me know if any additional tests would be
> helpful.
Thanks for letting me know. That patch set has already landed in Linus's
tree.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Sachin Sant <sachinp@linux.ibm.com>,
Russell King <linux@armlinux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Yinan Liu <yinan@linux.alibaba.com>,
linuxppc-dev@lists.ozlabs.org, Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ftrace: Have architectures opt-in for mcount build time sorting
Date: Fri, 28 Jan 2022 16:39:48 -0500 [thread overview]
Message-ID: <20220128163948.721c8b12@gandalf.local.home> (raw)
In-Reply-To: <YfRcC/ggq90jw7Uc@redhat.com>
On Fri, 28 Jan 2022 16:11:39 -0500
Joe Lawrence <joe.lawrence@redhat.com> wrote:
> The bisect finally landed on:
>
> 72b3942a173c387b27860ba1069636726e208777 is the first bad commit
> commit 72b3942a173c387b27860ba1069636726e208777
> Author: Yinan Liu <yinan@linux.alibaba.com>
> Date: Sun Dec 12 19:33:58 2021 +0800
>
> scripts: ftrace - move the sort-processing in ftrace_init
>
> and I can confirm that your updates today in "[for-linus][PATCH 00/10]
> tracing: Fixes for 5.17-rc1" fix or avoid the issue. I just wanted to
> add my report in case this adds any future complications for mcount
> build time sorting. Let me know if any additional tests would be
> helpful.
Thanks for letting me know. That patch set has already landed in Linus's
tree.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mark Rutland <mark.rutland@arm.com>,
Yinan Liu <yinan@linux.alibaba.com>,
Ard Biesheuvel <ardb@kernel.org>,
Kees Cook <keescook@chromium.org>,
Sachin Sant <sachinp@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ftrace: Have architectures opt-in for mcount build time sorting
Date: Fri, 28 Jan 2022 16:39:48 -0500 [thread overview]
Message-ID: <20220128163948.721c8b12@gandalf.local.home> (raw)
In-Reply-To: <YfRcC/ggq90jw7Uc@redhat.com>
On Fri, 28 Jan 2022 16:11:39 -0500
Joe Lawrence <joe.lawrence@redhat.com> wrote:
> The bisect finally landed on:
>
> 72b3942a173c387b27860ba1069636726e208777 is the first bad commit
> commit 72b3942a173c387b27860ba1069636726e208777
> Author: Yinan Liu <yinan@linux.alibaba.com>
> Date: Sun Dec 12 19:33:58 2021 +0800
>
> scripts: ftrace - move the sort-processing in ftrace_init
>
> and I can confirm that your updates today in "[for-linus][PATCH 00/10]
> tracing: Fixes for 5.17-rc1" fix or avoid the issue. I just wanted to
> add my report in case this adds any future complications for mcount
> build time sorting. Let me know if any additional tests would be
> helpful.
Thanks for letting me know. That patch set has already landed in Linus's
tree.
-- Steve
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-28 21:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 16:42 [PATCH] ftrace: Have architectures opt-in for mcount build time sorting Steven Rostedt
2022-01-27 16:42 ` Steven Rostedt
2022-01-27 16:42 ` Steven Rostedt
2022-01-27 18:23 ` Mark Rutland
2022-01-27 18:23 ` Mark Rutland
2022-01-27 18:23 ` Mark Rutland
2022-01-27 18:42 ` ftrace hangs waiting for rcu (was: Re: [PATCH] ftrace: Have architectures opt-in for mcount build time sorting) Sven Schnelle
2022-01-27 18:42 ` Sven Schnelle
2022-01-27 18:42 ` Sven Schnelle
2022-01-28 15:42 ` Mark Rutland
2022-01-28 15:42 ` Mark Rutland
2022-01-28 15:42 ` Mark Rutland
2022-01-28 16:08 ` ftrace hangs waiting for rcu Sven Schnelle
2022-01-28 16:08 ` Sven Schnelle
2022-01-28 16:08 ` Sven Schnelle
2022-01-28 16:11 ` Mark Rutland
2022-01-28 16:11 ` Mark Rutland
2022-01-28 16:11 ` Mark Rutland
2022-01-28 16:15 ` Paul E. McKenney
2022-01-28 16:15 ` Paul E. McKenney
2022-01-28 16:15 ` Paul E. McKenney
2022-01-28 17:47 ` Paul E. McKenney
2022-01-28 17:47 ` Paul E. McKenney
2022-01-28 17:47 ` Paul E. McKenney
2022-01-28 16:17 ` Sven Schnelle
2022-01-28 16:17 ` Sven Schnelle
2022-01-28 16:17 ` Sven Schnelle
2022-01-28 21:11 ` [PATCH] ftrace: Have architectures opt-in for mcount build time sorting Joe Lawrence
2022-01-28 21:11 ` Joe Lawrence
2022-01-28 21:11 ` Joe Lawrence
2022-01-28 21:39 ` Steven Rostedt [this message]
2022-01-28 21:39 ` Steven Rostedt
2022-01-28 21:39 ` Steven Rostedt
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=20220128163948.721c8b12@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=sachinp@linux.ibm.com \
--cc=yinan@linux.alibaba.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.