Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux: Kernel

Re: [PATCH] mips: fix endless loop when processing signals for kernel tasks

 

 

Linux kernel RSS feed   Index | Next | Previous | View Threaded


dmitry.adamushko at gmail

May 16, 2012, 11:37 PM

Post #1 of 1 (55 views)
Permalink
Re: [PATCH] mips: fix endless loop when processing signals for kernel tasks

So did I overlook something that makes it a non-issue on the recent mips?

On 5 April 2012 20:37, dimm <dmitry.adamushko [at] gmail> wrote:
> From: Dmitry Adamushko <dmitry.adamushka_ext [at] softathome>
>
> The problem occurs [1] when a kernel-mode task returns from a system
> call with a pending signal.
>
> A real-life scenario is a child of 'khelper' returning from a failed
> kernel_execve() in ____call_usermodehelper() [ kernel/kmod.c ].
> kernel_execve() fails due to a pending SIGKILL, which is the result of
> "kill -9 -1" (at least, busybox's init does it upon reboot).
>
> The loop is as follows:
>
> * syscall_exit_work:
>  - work_pending:            // start_of_the_loop
>  - work_notifysig:
>   - do_notify_resume()
>     - do_signal()
>       - if (!user_mode(regs)) return;
>  - resume_userspace         // TIF_SIGPENDING is still set
>  - work_pending             // so we call work_pending => goto
>                            // start_of_the_loop
>
> More information can be found in another LKML thread:
> http://www.serverphorums.com/read.php?12,457826
>
> [1] The problem was also reproduced on !CONFIG_VM86 x86, and the
> following fix was accepted.
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=29a2e2836ff9ea65a603c89df217f4198973a74f
>
> Signed-off-by: Dmitry Adamushko <dmitry.adamushko [at] gmail>
> Cc: Ralf Baechle <ralf [at] linux-mips>
> Cc: linux-mips [at] linux-mips
>
> --- arch/mips/kernel/entry.S.old        2012-04-05 10:57:12.500976124 +0200
> +++ arch/mips/kernel/entry.S    2012-04-05 11:21:24.128174358 +0200
> @@ -36,6 +36,11 @@ FEXPORT(ret_from_exception)
>  FEXPORT(ret_from_irq)
>        LONG_S  s0, TI_REGS($28)
>  FEXPORT(__ret_from_irq)
> +/*
> + * We can be coming here from a syscall done in the kernel space,
> + * e.g. a failed kernel_execve().
> + */
> +resume_userspace_check:
>        LONG_L  t0, PT_STATUS(sp)               # returning to kernel mode?
>        andi    t0, t0, KU_USER
>        beqz    t0, resume_kernel
> @@ -162,7 +167,7 @@ work_notifysig:                             # deal with pending s
>        move    a0, sp
>        li      a1, 0
>        jal     do_notify_resume        # a2 already loaded
> -       j       resume_userspace
> +       j       resume_userspace_check
>
>  FEXPORT(syscall_exit_work_partial)
>        SAVE_STATIC
>
>



--

-- Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Linux kernel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.