linux-kernel - RE: [PATCH] gcov: support GCC 12.1 and newer compilers

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]

Message-ID: <9b724e2af2d048c3a7f7f20ae0942ab6@AcuMS.aculab.com>
Date:   Mon, 17 Oct 2022 11:38:24 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Andrew Morton' <akpm@...ux-foundation.org>,
        Peter Oberparleiter <oberpar@...ux.ibm.com>
CC:     Martin Liška <mliska@...e.cz>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] gcov: support GCC 12.1 and newer compilers

From: Andrew Morton
> Sent: 17 October 2022 01:41
..
> The changelog doesn't tell us what the user-visible effects of this are
> (please, it should do so), but it sounds to me like those effects are
> "gcov is utterly busted".
> 
> So I'll add a cc:stable to this, so that people can use new gcc
> versions to build older kernels.

I can't help wondering what happens if you link a binary
compiled with an old gcc with one build with a new gcc?

This could easily happen with out of tree loadable modules.
Or just linking an old .a file into a userspace binary.

Now maybe the gcov data isn't used (I've not looked up what
it is for) but is sounds like something whose format should
be set in stone?

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)