linux-kernel - Re: [PATCH 7/9] jump label: sort jump table at build-time

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]

Date:	Fri,  9 Apr 2010 14:32:49 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	Jason Baron <jbaron@...hat.com>, linux-kernel@...r.kernel.org,
	mingo@...e.hu, mathieu.desnoyers@...ymtl.ca, hpa@...or.com,
	tglx@...utronix.de, rostedt@...dmis.org, andi@...stfloor.org,
	rth@...hat.com, mhiramat@...hat.com, fweisbec@...il.com,
	avi@...hat.com, "Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH 7/9] jump label: sort jump table at build-time

I think it just happens to come out harmless.  The relocs.c extraction
stuff doesn't actually care about the exact address to be relocated, it
only needs to know that a relocated value sits at a given place in the
binary.  The sorting rearranges the addresses in the text without
rearranging their corresponding relocs, but it's still the case that at
exactly each of those spots in text there is a relocated address.  The
boot-time "relocation" is just a blind adjustment to all those spots,
without reference to the original relocation details.  So it Just Works.
I'm not at all sure this is how we want things to be.  It's rather
nonobvious and fragile if we change any of the related magic.  But I think
it is entirely reliable in today's code that it will do the right thing.

Thanks,
Roland
--
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/