All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Micay <danielmicay@gmail.com>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] What ever happened to the kernel UBSan work?
Date: Tue, 17 Nov 2015 02:48:42 -0500	[thread overview]
Message-ID: <564ADBDA.10901@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

I remember seeing the UBSan submission at one point but it appears that
it never landed. It would be really nice to have it because among other
things it will encourage fixing all kinds of things that conflict with
features like SIZE_OVERFLOW and soon RAP. Maybe the kernel could even
begin migrating away from relying on signed overflow (by marking the
cases of intentional overflow with wrappers around the overflow
intrinsics like addw(a, b)).

There are also some niches where a 20% performance hit for something
like this makes sense (maybe only ~10% for just the parts that are
relevant to security, especially if it's just set to trap instead of
calling functions producing debug output).


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2015-11-17  7:48 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=564ADBDA.10901@gmail.com \
    --to=danielmicay@gmail.com \
    --cc=kernel-hardening@lists.openwall.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.