linux-kernel - Re: [PATCH] reduce export symbol CRC table size on 64-bit archs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <4A5B101E020000780000A284@vpn.id2.novell.com>
Date:	Mon, 13 Jul 2009 09:44:46 +0100
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Michal Marek" <mmarek@...e.cz>
Cc:	"Ingo Molnar" <mingo@...e.hu>, <tony.luck@...el.com>,
	"Jon Masters" <jonathan@...masters.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Rusty Russell" <rusty@...tcorp.com.au>,
	<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linux-modules@...r.kernel.org>, <hpa@...or.com>
Subject: Re: [PATCH] reduce export symbol CRC table size on 64-bit	
	 archs

>>> Michal Marek <mmarek@...e.cz> 13.07.09 10:11 >>>
>Jan Beulich napsal(a):
>> Actually I meanwhile think that module-init-tools can easily detect the changed
>> layout without any further kernel side adjustments: Since it is known that a
>> CRC always is a 32-bit value, simply checking whether the so-far-used 64-bit
>> value has more than 32 significant bits should suffice: If so, the new layout
>> is being used (with the symbol name starting at offset 4), else the old one is
>> in effect (name at offset 8). This ought to be a pretty trivial change to that
>> code.
>
>But old module-init-tools will continue reading garbage in this case.

And would you think returning nothing is significantly better than returning
garbage?

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/