Checksum tracking and tweaking
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | parser: fix the __attribute__ rulescripts/ | +1 | 3 replies | |
| 2/4 | Include extern information in dumpsscripts/ | +2 | 1 reply | |
| 3/4 | Track symbol checksum changesscripts/ scripts/ scripts/ | +239 | 2 replies | |
| 4/4 | Allow to ignore symbol checksum changesscripts/ scripts/ | +31 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [genksyms patch 0/4] Checksum tracking and tweaking
Sam and all,
we are having two kinds of problems with genksyms today: fake checksum changes without actual ABI changes, and changes which we would rather like to ignore (such as an additional field at the end of a structure that modules are not supposed to touch, for example).
I have thought about ways to improve genksyms and compute checksums differently to avoid those problems, but in the end I don't see a fundamentally better way. So here are some genksyms patches for at least making the checksums more easily manageable, if we cannot fully fix them.
In addition to the bugfixes (the first two patches), this allows genksyms to track checksum changes and report why a checksum changed (third patch), and to selectively ignore changes (fourth patch).
Any thoughts?
Thanks,
Andreas