Re: [RFC PATCH] crc generation fix for EXPORT_SYMBOL_GPL

[Ram Pai <linuxram@us.ibm.com>]

On Mon, 2006-02-06 at 15:09 +0100, Arjan van de Ven wrote:
> > Eventually we want to generate a tool that can report API changes across
> > kernel releases and put it in some friendly(docbook) format.
> 
> the CRC's are only very lightly related to API though (or even ABI) so I
> suspect this isn't too useful a thing to persue in the first place

actually the CRC's capture a pretty good picture of the changes to API
as well as ABI. The crc is run on the prototype of the exported symbol,
recursively expanding each and every datastructure involved in the
prototype. 

Hence it mostly captures the ABI signature of the exported symbols.  The
only part it misses is, it does not capture the GPL'ness of the exported
symbol. And that was what I was trying to fix, because changing the
export nature of the symbol changes the ABI. With the fix one would
be able to exactly detect API/ABI changes to exported symbols. 

Do you think its a bad idea still? Its a good indication for out-of-tree
modules that the ABI/API of some exported symbols they depend on, has
changed.  


>(using CRC I mean, documenting real API changes I can see being useful)

Sure. Nice to learn that this work will be of value. Also
looking for ideas on what information would be useful to report and in
what format. 

Thanks,
RP


> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/