From: Thomas Dillig <tdillig@stanford.edu>
To: kernel_org@digitalpeer.com, linux-kernel@vger.kernel.org,
eteo@redhat.com
Subject: Re: Null dereference errors in the kernel
Date: Mon, 17 Jul 2006 22:44:54 -0700 [thread overview]
Message-ID: <44BC7556.4000509@stanford.edu> (raw)
In-Reply-To: <44BC6B6B.8020509@digitalpeer.com>
Joshua Henderson wrote:
> Looked at the first 4. These are valid errors. Seems like a rather
> intelligent tool. When will this tool be publicly available?
We are currently aiming for a public release of the SATURN tool some
time in fall this year. Other students are also working on different
types of analyses/verification modules, which will slowly become ready
if everything goes as planned.
Eugene Teo wrote:
> I would be interested. Can you email bug reports so that bugs can be
> fixed?
> Also, please email security@kernel.org so that they can verify the reports
> should there be any false negatives.
Also, we will ready (e.g. double-check and pretty-print) more reports
and mail them (CC'ed to security@kernel.org) in chunks as soon as they
are ready. Please let us know if there is anything else you want us to do.
Thanks a lot, it's exciting to hear back from developers after working
on this for a long time :)
-Isil & Tom
next prev parent reply other threads:[~2006-07-18 5:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 3:49 Null dereference errors in the kernel Thomas Dillig
2006-07-18 5:02 ` Joshua Henderson
2006-07-18 5:44 ` Thomas Dillig [this message]
2006-07-18 9:24 ` Daniel Drake
2006-07-18 12:45 ` Dmitry Torokhov
2006-07-18 14:02 ` Daniel Drake
2006-07-18 16:40 ` Dave Jones
2006-07-18 22:37 ` Peter Osterlund
2006-07-18 20:55 ` Stefan Richter
2006-07-18 21:16 ` Luiz Fernando N. Capitulino
2006-07-18 21:30 ` Andreas Schwab
2006-07-18 22:46 ` Luiz Fernando N. Capitulino
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=44BC7556.4000509@stanford.edu \
--to=tdillig@stanford.edu \
--cc=eteo@redhat.com \
--cc=kernel_org@digitalpeer.com \
--cc=linux-kernel@vger.kernel.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 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.