From: Andreas Gruenbacher <agruen@suse.de>
To: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: [genksyms patch 0/4] Checksum tracking and tweaking
Date: Mon, 21 Jul 2008 04:28:23 +0200 [thread overview]
Message-ID: <20080721022823.896799736@suse.de> (raw)
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
next reply other threads:[~2008-07-21 3:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 2:28 Andreas Gruenbacher [this message]
2008-07-21 2:28 ` [genksyms patch 1/4] parser: fix the __attribute__ rule Andreas Gruenbacher
2008-07-30 20:43 ` Sam Ravnborg
2008-07-30 22:03 ` Andreas Gruenbacher
2008-07-31 21:17 ` Sam Ravnborg
2008-07-21 2:28 ` [genksyms patch 2/4] Include extern information in dumps Andreas Gruenbacher
2008-07-31 21:18 ` Sam Ravnborg
2008-07-21 2:28 ` [genksyms patch 3/4] Track symbol checksum changes Andreas Gruenbacher
2008-09-03 5:02 ` Andrew Morton
2008-09-03 8:13 ` Andreas Gruenbacher
2008-07-21 2:28 ` [genksyms patch 4/4] Allow to ignore " Andreas Gruenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080721022823.896799736@suse.de \
--to=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox