public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, mingo@elte.hu
Subject: [PATCH 0/9] Series to make copy_from_user to a stack slot provable right
Date: Sat, 26 Sep 2009 20:49:51 +0200	[thread overview]
Message-ID: <20090926204951.424e567e@infradead.org> (raw)

[PATCH 0/9] Series to make copy_from_user to a stack slot provable right

This series contains a series of patches that, when applied, make every
copy_from_user() in a make allyesconfig to a (direct) stack slot
provable-by-gcc to have a correct size.

This is useful because if we fix all of these, we can make the non-provable
case an error, as an indication of a possible security hole.

Now the series has 4 types of patches
1) changes where the original code really was missing checks
2) changes where the checks were coded so complex and games were played with
   types, that I (and the compiler) couldn't be sure if it was correct or
   not
3) changes where we're hitting a small gcc missing optimization, but where
   a simplification of the code allows gcc to prove things anyway.
   (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41477 is filed for this)
4) a case in sys_socketcall where Dave Miller and co were very smart in
   optimizing the code to the point where it's not reasonable for gcc
   to realize the result is ok.



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

             reply	other threads:[~2009-09-26 18:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 18:49 Arjan van de Ven [this message]
2009-09-26 18:50 ` [PATCH 1/9] Fix bound checks for copy_from_user in the acpi /proc code Arjan van de Ven
2009-09-26 18:50 ` [PATCH 2/9] Simplify bound checks in nvram for copy_from_user Arjan van de Ven
2009-09-26 18:51 ` [PATCH 3/9] Add bound checks in wext " Arjan van de Ven
2009-09-26 18:51 ` [PATCH 4/9] Simplify bound checks in the MTRR code Arjan van de Ven
2009-10-02 18:36   ` [tip:x86/urgent] x86: " tip-bot for Arjan van de Ven
2009-09-26 18:52 ` [PATCH 5/9] Add bound checks in acpi/video for copy_from_user Arjan van de Ven
2009-09-26 18:52 ` [PATCH 6/9] Simplify bound checks in cifs " Arjan van de Ven
2009-09-26 18:53 ` [PATCH 7/9] Simplify bound checks in capabilities " Arjan van de Ven
2009-09-29  5:55   ` Dave Airlie
2009-09-29  9:24     ` Arjan van de Ven
2009-10-01 22:34       ` James Morris
2009-09-26 18:54 ` [PATCH 8/9] Add explicit bound checks in mm/migrate.c Arjan van de Ven
2009-09-30 22:20   ` Andrew Morton
2009-10-01  5:54     ` KOSAKI Motohiro
     [not found]   ` <tip-b925585039cf39275c2e0e57512e5df27fa73aad@git.kernel.org>
2009-12-13 23:38     ` [tip:x86/urgent] mm: Adjust do_pages_stat() so gcc can see copy_from_user() is safe KOSAKI Motohiro
2009-09-26 18:54 ` [PATCH 9/9] Add explicit bound checks in net/socket.c Arjan van de Ven
2009-09-26 19:01   ` Cyrill Gorcunov
2009-09-26 19:05     ` Arjan van de Ven
2009-09-26 19:23     ` Arjan van de Ven
2009-09-26 19:35       ` Cyrill Gorcunov
2009-09-28 19:57       ` David Miller

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=20090926204951.424e567e@infradead.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox