[PATCH] powerpc/mm: add devmem_is_allowed() for STRICT_DEVMEM checking

2011-01-31 Thread Steve Best
Provide devmem_is_allowed() routine to restrict access to kernel memory from userspace. Set CONFIG_STRICT_DEVMEM config option to switch on checking. Signed-off-by: Steve Best diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug index 2d38a50..6805d5d 100644 --- a

Re: [PATCH] powerpc/mm: add devmem_is_allowed() for STRICT_DEVMEM checking

2011-02-01 Thread Steve Best
On Mon, 2011-01-31 at 13:40 -0600, Scott Wood wrote: > On Mon, 31 Jan 2011 14:16:00 -0500 > Steve Best wrote: > > > Provide devmem_is_allowed() routine to restrict access to kernel > > memory from userspace. > > Set CONFIG_STRICT_DEVMEM config o

[PATCH] powerpc/mm: add devmem_is_allowed() for STRICT_DEVMEM checking

2011-06-14 Thread Steve Best
Provide devmem_is_allowed() routine to restrict access to kernel memory from userspace. Set CONFIG_STRICT_DEVMEM config option to switch on checking. Signed-off-by: Steve Best diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug index e72dcf6..e1aab6b

Re: [PATCH] powerpc/mm: add devmem_is_allowed() for STRICT_DEVMEM checking

2011-06-14 Thread Steve Best
On Tue, 2011-06-14 at 12:30 -0500, Nathan Lynch wrote: > Hi Steve, > > On Tue, 2011-06-14 at 12:58 -0400, Steve Best wrote: > > diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug > > index e72dcf6..e1aab6b 100644 > > --- a/arch/powerpc/Kconfig.d

[PATCH] powerpc: Fix integer constant warning

2010-06-07 Thread Steve Best
Fix ppc arch/powerpc/boot/addRamDisk.c:277: warning: integer constant is too large for 'long' type Signed-off-by: Steve Best diff -purN linux.2.6.orig/arch/powerpc/boot/addRamDisk.c linux.2.6/arch/powerpc/boot/addRamDisk.c --- linux.2.6.orig/arch/powerpc/boot/addRamDisk.c 2010

Re: [PATCH] powerpc: Fix integer constant warning

2010-06-09 Thread Steve Best
On Tue, 2010-06-08 at 14:12 +0100, David Howells wrote: > Steve Best wrote: > > > -#define KERNELBASE (0xc000) > > +#define KERNELBASE (0xc000ULL) > > Is this the right fix? The code producing the warning is subtracting > 0xc000 f