From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Greg KH <greg@kroah.com>
Cc: Sandy Harris <sandyinchina@gmail.com>,
kernel-hardening@lists.openwall.com
Subject: Re: Checked C?
Date: Sun, 9 Sep 2018 12:56:47 -0400 [thread overview]
Message-ID: <20180909165647.GC22251@thunk.org> (raw)
In-Reply-To: <20180909125912.GA17863@kroah.com>
On Sun, Sep 09, 2018 at 02:59:12PM +0200, Greg KH wrote:
> On Sun, Sep 09, 2018 at 08:22:44AM -0400, Sandy Harris wrote:
> > Slashdot reports that Microsoft have come up with something they call
> > "checked C". It claims to prevent a wide variety of memory & pointer
> > bugs, using a mix of compile-time and run-time checks, at moderate
> > overheads.
> >
> > Implementation is as extensions to Clang so it might be hard to apply
> > to the kernel which I think has some GNU-isms. Perhaps still worth a
> > look?
What would be really interesting would be implementing the Microsoft
extensions as Clang plugins, so the kernel changes don't require
distributions to ship a modified Clang.
Whoever does this will need to remember that kernel modifications need
to work with:
* Clang with the extensions
* Clang without the extensions (in case the extensions are Clang
version dependent, and the system has a Clang which is too old).
* Gcc without the extensions
We've been doing that sort of thing already, using CPP magic, so there
are plenty of examples about ways of doing that.
- Ted
next prev parent reply other threads:[~2018-09-09 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 12:22 Checked C? Sandy Harris
2018-09-09 12:59 ` Greg KH
2018-09-09 16:56 ` Theodore Y. Ts'o [this message]
2018-09-09 18:24 ` Boris Lukashev
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=20180909165647.GC22251@thunk.org \
--to=tytso@mit.edu \
--cc=greg@kroah.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=sandyinchina@gmail.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 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.