From: Andi Kleen <andi@firstfloor.org>
To: Marcelo Sousa <marceloabsousa@gmail.com>
Cc: linux-kernel@vger.kernel.org, msousa@cs.ox.ac.uk
Subject: Re: Lightweight type analysis for memory safety through verification of API uses
Date: Mon, 23 Sep 2013 21:11:45 -0700 [thread overview]
Message-ID: <87fvsudfjy.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CACu8kRTN7XoTxvcFHQ=7N-rUGoUePS43EwRKax25mqBjzEXNVg@mail.gmail.com> (Marcelo Sousa's message of "Tue, 17 Sep 2013 14:00:48 +0100")
Marcelo Sousa <marceloabsousa@gmail.com> writes:
> I've designed and implemented a tool similar to sparse and CQUAL that
> does type inference of user specified type qualifiers, e.g. iomem. It
> receives an API specification with the type qualifiers and also a
> partial order, e.g. IOAddr is not compatible with KernelAddr and
> ioremap returns a pointer to IOAddr while __kmalloc returns a pointer
> to a KernelAddr.
Tracking iomem is ultimatively not very interesting, as in many common
architectures it's just a normal pointer.
__user is much more interesting, as that is real security bugs.
You can probably find some in standard security advisories.
Really interesting would be static lock set tracking for pointers
and similar.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-09-24 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 13:00 Lightweight type analysis for memory safety through verification of API uses Marcelo Sousa
2013-09-24 4:11 ` Andi Kleen [this message]
2013-09-24 10:33 ` Marcelo Sousa
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=87fvsudfjy.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marceloabsousa@gmail.com \
--cc=msousa@cs.ox.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.