From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: Tree for September 18
Date: Thu, 18 Sep 2008 15:20:38 -0700 [thread overview]
Message-ID: <20080918152038.7b146f23.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080918174108.3357c3d2.sfr@canb.auug.org.au>
On Thu, 18 Sep 2008 17:41:08 +1000
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> (patches at
> http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/)
Anyone using this kernel shold apply this x86 fix:
--- a/include/linux/uaccess.h~uaccess-fix-parameters-inversion-for-__copy_from_user_inatomic
+++ a/include/linux/uaccess.h
@@ -78,7 +78,7 @@ static inline unsigned long __copy_from_
\
set_fs(KERNEL_DS); \
pagefault_disable(); \
- ret = __copy_from_user_inatomic((__force typeof(retval) __user *)(addr), &(retval), sizeof(retval)); \
+ ret = __copy_from_user_inatomic(&(retval), (__force typeof(retval) __user *)(addr), sizeof(retval)); \
pagefault_enable(); \
set_fs(old_fs); \
ret; \
_
to prevent a storm of warnings like
[ 58.694606] SLAB: cache with size 16384 has lost its name
[ 58.694773] SLAB: cache with size 8192 has lost its name
[ 58.694940] SLAB: cache with size 8192 has lost its name
[ 58.695101] SLAB: cache with size 4096 has lost its name
[ 58.695260] SLAB: cache with size 4096 has lost its name
[ 58.695418] SLAB: cache with size 2048 has lost its name
plus probably other more nasty things.
next prev parent reply other threads:[~2008-09-18 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 7:41 linux-next: Tree for September 18 Stephen Rothwell
2008-09-18 22:20 ` Andrew Morton [this message]
2008-09-18 23:11 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-09-18 6:40 Stephen Rothwell
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=20080918152038.7b146f23.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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