linux-kernel - Re: [PATCH] x86/ftrace: Exclude functions in head64.c from function-tracing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 27 Jun 2017 17:44:03 +0300
From:   "Kirill A. Shutemov" <kirill@...temov.name>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        Ingo Molnar <mingo@...nel.org>, x86@...nel.org,
        Fengguang Wu <fengguang.wu@...el.com>, lkp@...org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/ftrace: Exclude functions in head64.c from
 function-tracing

On Tue, Jun 27, 2017 at 09:38:25AM -0400, Steven Rostedt wrote:
> On Tue, 27 Jun 2017 14:59:48 +0300
> "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com> wrote:
> 
> > We've moved most logic of early boot up from startup_64() written in
> > assembly to __startup_64() written in C.
> > 
> > Fengguang reported breakage due to the change. It was tracked down to
> > CONFIG_FUNCTION_TRACER being enabled.
> 
> Is this due to code that is in linux-next or is this issue currently in
> mainline?
> 
> If it is in linux-next, I'll give you:
> 
>  Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
> 
> and you can take it. If the issue happens in current mainline, then I'll
> take it and push it out.

It's in -next.

Fixes: c88d71508e36 ("x86/boot/64: Rewrite startup_64() in C")

Although, I'm not sure if commit-id is stable yet.

-- 
 Kirill A. Shutemov