From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "SystemTap" <systemtap@sources.redhat.com>
Subject: FW: [Bug translator/901] static validator
Date: Tue, 28 Feb 2006 02:40:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06860877@scsmsx403.amr.corp.intel.com> (raw)
I've checked in a static validator for SystemTap modules, and I would
like to get feedback on it. You can find it in 'src/safety/safety.py'.
It checks modules for legal external references, and parses the
disassembly for legal opcodes.
For the allowed references file, I simply compiled all of the sample and
buildok scripts I could find and added all of their references to the
allowed list. I did only minimal verification on this, so it could very
well need some pruning.
For allowed opcodes, I've compiled the list for i686 and x86_64. I
believe everything is covered & allowable in there, but it's of course
open for review. The only surprise to me was 'movaps', but that
instruction is actually very common within the kernel.
I welcome comments and suggestions for improvement...
Thanks,
Josh
joshua dot i dot stone at intel dot com wrote:
> ------- Additional Comments From joshua dot i dot stone at intel dot
> com 2006-02-28 02:29 -------
> A static safety checker has been committed to CVS. It checks for
> whitelisted opcodes and external references, with initial support
> for i686 and x86_64. Adding other platforms is mostly a matter of
> defining the allowed opcodes...
reply other threads:[~2006-02-28 2:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CBDB88BFD06F7F408399DBCF8776B3DC06860877@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).