linux/arch/alpha, branch v3.12

Remove GENERIC_HARDIRQ config option

2013-09-13T13:09:52Z

After the last architecture switched to generic hard irqs the config options HAVE_GENERIC_HARDIRQS & GENERIC_HARDIRQS and the related code for !CONFIG_GENERIC_HARDIRQS can be removed. Signed-off-by: Martin Schwidefsky

arch: mm: pass userspace fault flag to generic fault handler

2013-09-12T22:38:01Z

Unlike global OOM handling, memory cgroup code will invoke the OOM killer in any OOM situation because it has no way of telling faults occuring in kernel context - which could be handled more gracefully - from user-triggered faults. Pass a flag that identifies faults originating in user space from the architecture-specific fault handlers to generic code so that memcg OOM handling can be improved. Signed-off-by: Johannes Weiner Reviewed-by: Michal Hocko Cc: David Rientjes Cc: KAMEZAWA Hiroyuki Cc: azurIt Cc: KOSAKI Motohiro Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

kernel-wide: fix missing validations on get/put/__copy_to/__copy_from_user()

2013-09-11T22:58:18Z

I found the following pattern that leads in to interesting findings: grep -r "ret.*|=.*__put_user" * grep -r "ret.*|=.*__get_user" * grep -r "ret.*|=.*__copy" * The __put_user() calls in compat_ioctl.c, ptrace compat, signal compat, since those appear in compat code, we could probably expect the kernel addresses not to be reachable in the lower 32-bit range, so I think they might not be exploitable. For the "__get_user" cases, I don't think those are exploitable: the worse that can happen is that the kernel will copy kernel memory into in-kernel buffers, and will fail immediately afterward. The alpha csum_partial_copy_from_user() seems to be missing the access_ok() check entirely. The fix is inspired from x86. This could lead to information leak on alpha. I also noticed that many architectures map csum_partial_copy_from_user() to csum_partial_copy_generic(), but I wonder if the latter is performing the access checks on every architectures. Signed-off-by: Mathieu Desnoyers Cc: Richard Henderson Cc: Ivan Kokshaysky Cc: Matt Turner Cc: Jens Axboe Cc: Oleg Nesterov Cc: David Miller Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

oprofilefs_create_...() do not need superblock argument

2013-09-04T02:52:48Z

same story as with oprofilefs_mkdir() Signed-off-by: Al Viro

oprofilefs_mkdir() doesn't need superblock argument

2013-09-04T02:52:47Z

it's always equal to ->d_sb of the second argument (parent dentry), due to either being literally that, or ->d_sb of parent's parent. Signed-off-by: Al Viro

oprofile: don't bother with passing superblock to ->create_files()

2013-09-04T02:52:46Z

Signed-off-by: Al Viro

alpha: Use handle_percpu_irq for the timer interrupt

2013-07-19T20:54:26Z

Signed-off-by: Matt Turner Signed-off-by: Richard Henderson

alpha: Force the user-visible HZ to a constant 1024.

2013-07-19T20:54:26Z

This kernel/user split was done long ago for other architectures. Signed-off-by: Matt Turner Signed-off-by: Richard Henderson

alpha: Don't if-out dp264_device_interrupt.

2013-07-19T20:54:26Z

The code as written is correct, and will be used by QEMU emulation. Signed-off-by: Matt Turner Signed-off-by: Richard Henderson

alpha: Use __builtin_alpha_rpcc

2013-07-19T20:54:25Z

As introduced in gcc 3.2. Signed-off-by: Matt Turner Signed-off-by: Richard Henderson

linux/arch/alpha, branch v3.12

Remove GENERIC_HARDIRQ config option

arch: mm: pass userspace fault flag to generic fault handler

kernel-wide: fix missing validations on __get/__put/__copy_to/__copy_from_user()

oprofilefs_create_...() do not need superblock argument

oprofilefs_mkdir() doesn't need superblock argument

oprofile: don't bother with passing superblock to ->create_files()

alpha: Use handle_percpu_irq for the timer interrupt

alpha: Force the user-visible HZ to a constant 1024.

alpha: Don't if-out dp264_device_interrupt.

alpha: Use __builtin_alpha_rpcc

kernel-wide: fix missing validations on get/put/__copy_to/__copy_from_user()