linux-kernel - Re: [PATCH] fully support linker generated .eh_frame

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]

Date:	Wed, 06 Dec 2006 07:57:52 +0000
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>
Cc:	"Randy Dunlap" <randy.dunlap@...cle.com>,
	"Andi Kleen" <ak@...e.de>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fully support linker generated .eh_frame_hdr
	section

>>> Jan Engelhardt <jengelh@...ux01.gwdg.de> 05.12.06 20:52 >>>
>
>>>> Now that binutils' ld is able to properly populate .eh_frame_hdr in the
>>>> Linux kernel case, here's a patch to add some functionality to the Dwarf2
>>>> unwinder to actually be able to make use of this (applies on firstfloor
>>>> tree with the previously sent patch to add debug output, but not on plain
>>>> 2.6.19).
>>>
>>>Requires what version of binutils / ld?
>>
>>mainline - the second of the required patches went in just yesterday.
>
>Which means people using distros will have it in some 6 months, unless 
>vendors give an earlier update.

That's not the point here - the point is that the kernel should be ready to take
advantage of this whenever somebody tries to build with newer binutils. Also,
the patch adds a previously missing check that would result in not creating a
runtime allocated table (assuming the linker created one is usable), but failing
to read from that table during later lookups (resulting in the originally
observed long boot time due to lockdep making heavy use of this code).

Jan
-
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/