Re: [WTF?] sys_tas() on m32r

[Andrew Morton <akpm@osdl.org>]

Al Viro <viro@ftp.linux.org.uk> wrote:
>
> asmlinkage int sys_tas(int *addr)
> {
>         int oldval;
>         unsigned long flags;
> 
>         if (!access_ok(VERIFY_WRITE, addr, sizeof (int)))
>                 return -EFAULT;
>         local_irq_save(flags);
>         oldval = *addr;
>         if (!oldval)
>                 *addr = 1;
>         local_irq_restore(flags);
>         return oldval;
> }
> in arch/m32r/kernel/sys_m32r.c.  Trivial oops *AND* ability to trigger
> IO with interrupts disabled.

Yeah.  I pointed this out to Takata in October last year and then promptly
forgot about it.  It's rather amazing that this code (which appears to be in
live use in linuxthreads) hasn't generated oopses.

The problem is that touching *addr will generate an oops if that page isn't
paged in.  If we convert it to use get_user() then that's an improvement,
but we must not run get_user() under spinlock or local_irq_disable().

The safe-and-slow way to do this is to pin the page with get_user_pages().

A smarter way to do it is to do something similar to filemap_copy_from_user():

	for ( ; ; ) {
		get_user(c, addr);
		inc_preempt_count();
		if (get_user(oldval, addr)) {
			dec_preempt_count();
			continue;
		}
		if (!oldval && put_user(1, addr)) {
			dec_preempt_count();
			continue;
		}
		dec_preempt_count();
		break;
	}

ie: try to fault the page in with get_user(), then switch into atomic mode
and try the memory access.  If the page isn't there any more, get_user()
and put_user() will return -EFAULT without entering the pagefault handler
(the in_atomic() test in do_page_fault()) so we can just retry the pagein. 



The above all assumes CONFIG_MMU.  I guess sys_tas() as it stands is OK if
!CONFIG_MMU.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/