linux-kernel - Re: [PATCH 4.14 5/6] ARM: 8788/1: ftrace: remove old mcount support

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] [day] [month] [year] [list]

Message-ID: <YcB5b65dVUIhzgIh@kroah.com>
Date:   Mon, 20 Dec 2021 13:39:11 +0100
From:   Greg KH <greg@...ah.com>
To:     Anders Roxell <anders.roxell@...aro.org>
Cc:     stable@...r.kernel.org, linux-kernel@...r.kernel.org,
        woojung.huh@...rochip.com, UNGLinuxDriver@...rochip.com,
        davem@...emloft.net, netdev@...r.kernel.org,
        linux-usb@...r.kernel.org, clang-built-linux@...glegroups.com,
        ulli.kroll@...glemail.com, linux@...linux.org.uk,
        linux-arm-kernel@...ts.infradead.org, amitkarwar@...il.com,
        nishants@...vell.com, gbhat@...vell.com, huxinming820@...il.com,
        kvalo@...eaurora.org, linux-wireless@...r.kernel.org,
        rostedt@...dmis.org, mingo@...hat.com, dmitry.torokhov@...il.com,
        ndesaulniers@...gle.com, nathan@...nel.org,
        linux-input@...r.kernel.org, Stefan Agner <stefan@...er.ch>,
        Russell King <rmk+kernel@...linux.org.uk>
Subject: Re: [PATCH 4.14 5/6] ARM: 8788/1: ftrace: remove old mcount support

On Mon, Dec 20, 2021 at 01:25:05PM +0100, Anders Roxell wrote:
> From: Stefan Agner <stefan@...er.ch>
> 
> commit d3c61619568c88d48eccd5e74b4f84faa1440652 upstream.
> 
> Commit cafa0010cd51 ("Raise the minimum required gcc version to 4.6")

That commit is in 4.19, not 4.14.  So are you SURE this is ok for 4.14
and older kernels?

> raised the minimum GCC version to 4.6. Old mcount is only required for
> GCC versions older than 4.4.0. Hence old mcount support can be dropped
> too.

And as I asked on the 4.19 submission of this patch, what does this have
to do with clang?

thanks,

greg k-h