linux-kernel - Re: [PATCH] scripts/recordmcount.pl: Support build with -ffunction-sections.

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: <1351622134.4004.17.camel@gandalf.local.home>
Date:	Tue, 30 Oct 2012 14:35:34 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Will Newton <will.newton@...il.com>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] scripts/recordmcount.pl: Support build with
 -ffunction-sections.

On Tue, 2012-10-30 at 17:43 +0000, Will Newton wrote:

> Ok, well we are only concerned with C compiled code, otherwise there
> would be no calls to mcount? The only way I can think of to cause code
> to be emitted in a section of this type is to use the section
> attribute. A quick grep for __attribute__(__section__ or __section
> does not turn up any sections that are named .text.* on any
> architecture (freed or not).
> 
> Is there any other case I have missed? I also did a grep for .text.
> more generally and didn't see anything that looked problematic
> (although it is mainly .S files so not relevant).

If you feel confident enough, then I'm fine with it. But if any more
network cards get bricked, I'm blaming you.

 ;-)

> 
> >>
> >> > Second, most archs today do not use recordmcount.pl. They use the new
> >> > recordmcount.c file.
> >>
> >> Ok, thanks for letting me know. Is the plan to switch over to
> >> recordmcount.c exclusively at some point?
> >
> > When all the archs convert.
> 
> I'll rework my patch against recordmcount.c once I have it working.

OK, thanks.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/