linux-kernel - Re: [REGRESSION] Recent change to kernel spikes out ccache/distcc

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]

Message-Id: <49647A9E.76E4.0078.0@novell.com>
Date:	Wed, 07 Jan 2009 08:49:18 +0000
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Al Viro" <viro@...IV.linux.org.uk>
Cc:	<ccache@...ts.samba.org>, "Theodore Ts'o" <tytso@....edu>,
	"Sam Ravnborg" <sam@...nborg.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] Recent change to kernel spikes out
	 ccache/distcc

>>> Al Viro <viro@...IV.linux.org.uk> 07.01.09 06:10 >>>
>On Tue, Jan 06, 2009 at 10:15:26AM -0500, Theodore Ts'o wrote:
>> Or, if that's too complicated, maybe it would be worthwhile to have
>> kbuild create its own specialized ccache system?  Note that the last two
>> solutions rule out using distcc, unless we can encapsulate the build
>> process from a series of Makefile macros to a shell or C program, which
>> could then be injected to the remote host system to be executed by
>> distcc.  One value of doing that is the CRC or MD5 of the shell script
>> could be used as the version tag for the cache system.
>
>Ho-hum...  Could somebody explain why the hell had we switched to this
>"intermediate .s" approach, anyway?  It's not as if we couldn't run
>objcopy after what we used to do...

Because objcopy wouldn't remove the __crc_* symbols the way the
object files were generated previously. I explored all possibilities I could
think of, with that two step process being the last, but the only one that
had the intended effect. In the end I queried the binutils list, and got
confirmation that there's no (existing) way to get rid of symbols used in
relocations in an already existing object file without corrupting it.

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/