linux-kernel - Re: discarded `.exit.text' debugging?

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: <Pine.LNX.4.64.0810261522350.15317@anakin>
Date:	Sun, 26 Oct 2008 19:32:54 +0100 (CET)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: discarded `.exit.text' debugging?

On Mon, 20 Oct 2008, Geert Uytterhoeven wrote:
> Last night I got these in my build logs:
> 
> | `.exit.text' referenced in section `.init.text' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
> | `.exit.text' referenced in section `.data' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o
> 
> i.e. not much context. Is there an easy way to find out who's the
> offender?

I also didn't get any section mismatch warnings about them with
CONFIG_DEBUG_SECTION_MISMATCH=y.

So I went the hard way (i.e. maual bisection on CONFIG symbols) and found 2
bogus __exit marks in drivers/rtc/rtc-ds3234.c and drivers/hwmon/w83781d.c.

Patches to fix them have been sent.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
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/