Re: [patch 1/8] genksyms: track symbol checksum changes

[Sam Ravnborg <sam@ravnborg.org>]

On Mon, Dec 01, 2008 at 02:21:01PM -0800, akpm@linux-foundation.org wrote:
> From: Andreas Gruenbacher <agruen@suse.de>
> 
> Sometimes it is preferable to avoid changes of exported symbol checksums
> (to avoid breaking externally provided modules).  When a checksum change
> occurs, it can be hard to figure out what caused this change: underlying
> types may have changed, or additional type information may simply have
> become available at the point where a symbol is exported.
> 
> Add a new --reference option to genksyms which allows it to report why
> checksums change, based on the type information dumps it creates with the
> --dump-types flag.  Genksyms will read in such a dump from a previous run,
> and report which symbols have changed (and why).
> 
> The behavior can be controlled for an entire build as follows: If
> KBUILD_SYMTYPES is set, genksyms uses --dump-types to produce *.symtypes
> dump files.  If any *.symref files exist, those will be used as the
> reference to check against.  If KBUILD_PRESERVE is set, checksum changes
> will fail the build.
> 
> Signed-off-by: Andreas Gruenbacher <agruen@suse.de>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

Applied.

	Sam