<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/tools/testing/selftests/user, branch v3.16</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/tools/testing/selftests/user?h=v3.16</id>
<link rel='self' href='https://git.amat.us/linux/atom/tools/testing/selftests/user?h=v3.16'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-01-24T00:36:57Z</updated>
<entry>
<title>test: check copy_to/from_user boundary validation</title>
<updated>2014-01-24T00:36:57Z</updated>
<author>
<name>Kees Cook</name>
<email>keescook@chromium.org</email>
</author>
<published>2014-01-23T23:54:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3e2a4c183ace8708c69f589505fb82bb63010ade'/>
<id>urn:sha1:3e2a4c183ace8708c69f589505fb82bb63010ade</id>
<content type='text'>
To help avoid an architecture failing to correctly check kernel/user
boundaries when handling copy_to_user, copy_from_user, put_user, or
get_user, perform some simple tests and fail to load if any of them
behave unexpectedly.

Specifically, this is to make sure there is a way to notice if things
like what was fixed in commit 8404663f81d2 ("ARM: 7527/1: uaccess:
explicitly check __user pointer when !CPU_USE_DOMAINS") ever regresses
again, for any architecture.

Additionally, adds new "user" selftest target, which loads this module.

Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Cc: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
