linux.git/arch/frv/kernel, branch v2.6.37

BKL: remove extraneous #include

2010-11-17T16:59:32+00:00

The big kernel lock has been removed from all these files at some point,
leaving only the #include.

Remove this too as a cleanup.

Signed-off-by: Arnd Bergmann 
Signed-off-by: Linus Torvalds

ptrace: cleanup arch_ptrace() on frv

2010-10-28T01:03:10+00:00

Use new 'regno', 'datap' variables in order to remove duplicated
expressions and unnecessary castings. Alse remove checking @addr
less than 0 because addr is now unsigned.

Signed-off-by: Namhyung Kim 
Cc: David Howells 
Cc: "Daniel K." 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ptrace: change signature of arch_ptrace()

2010-10-28T01:03:10+00:00

Fix up the arguments to arch_ptrace() to take account of the fact that
@addr and @data are now unsigned long rather than long as of a preceding
patch in this series.

Signed-off-by: Namhyung Kim 
Cc: 
Acked-by: Roland McGrath 
Acked-by: David Howells 
Acked-by: Geert Uytterhoeven 
Acked-by: David S. Miller 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

frv: double syscall restarts, syscall restart in sigreturn()

2010-09-20T17:44:38+00:00

We need to make sure that only the first do_signal() to be handled on
the way out syscall will bother with syscall restarts; additionally, the
check on the "signal has user handler" path had been wrong - compare
with restart prevention in sigreturn()...

Signed-off-by: Al Viro 
Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds

frv: handling of restart into restart_syscall is fscked

2010-09-20T17:44:38+00:00

do_signal() should place the syscall number in gr7, not gr8 when
handling ERESTART_WOULDBLOCK.

Signed-off-by: Al Viro 
Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds

frv: avoid infinite loop of SIGSEGV delivery

2010-09-20T17:44:37+00:00

Use force_sigsegv() rather than force_sig(SIGSEGV, ...) as the former
resets the SEGV handler pointer which will kill the process, rather than
leaving it open to an infinite loop if the SEGV handler itself caused a
SEGV signal.

Signed-off-by: Al Viro 
Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds

frv: fix address verification holes in setup_frame/setup_rt_frame

2010-09-20T17:44:37+00:00

a) sa_handler might be maliciously set to point to kernel memory;
   blindly dereferencing it in FDPIC case is a Bad Idea(tm).

b) I'm not sure you need that set_fs(USER_DS) there at all, but if you
   do, you'd better do it *before* checking the frame you've decided to
   use with access_ok(), lest sigaltstack() becomes a convenient
   roothole.

Signed-off-by: Al Viro 
Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds

frv: restart_block.fn needs to be reset on sigreturn

2010-09-20T17:44:37+00:00

Reset restart_block.fn on executing a sigreturn such that any currently
pending system call restarts will be forced to return -EINTR.

Signed-off-by: Al Viro 
Signed-off-by: David Howells 
Signed-off-by: Linus Torvalds

Make do_execve() take a const filename pointer

2010-08-18T01:07:43+00:00

Make do_execve() take a const filename pointer so that kernel_execve() compiles
correctly on ARM:

arch/arm/kernel/sys_arm.c:88: warning: passing argument 1 of 'do_execve' discards qualifiers from pointer target type

This also requires the argv and envp arguments to be consted twice, once for
the pointer array and once for the strings the array points to.  This is
because do_execve() passes a pointer to the filename (now const) to
copy_strings_kernel().  A simpler alternative would be to cast the filename
pointer in do_execve() when it's passed to copy_strings_kernel().

do_execve() may not change any of the strings it is passed as part of the argv
or envp lists as they are some of them in .rodata, so marking these strings as
const should be fine.

Further kernel_execve() and sys_execve() need to be changed to match.

This has been test built on x86_64, frv, arm and mips.

Signed-off-by: David Howells 
Tested-by: Ralf Baechle 
Acked-by: Russell King 
Signed-off-by: Linus Torvalds

Mark arguments to certain syscalls as being const

2010-08-13T23:53:13+00:00

Mark arguments to certain system calls as being const where they should be but
aren't.  The list includes:

 (*) The filename arguments of various stat syscalls, execve(), various utimes
     syscalls and some mount syscalls.

 (*) The filename arguments of some syscall helpers relating to the above.

 (*) The buffer argument of various write syscalls.

Signed-off-by: David Howells 
Acked-by: David S. Miller 
Signed-off-by: Linus Torvalds