lkml.org 
[lkml]   [2015]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] signals: Generate warning when flush_signals() is called from non-kthread context
On Mon, 4 May 2015, Oleg Nesterov wrote:

> > All the calls in md.c are in a kernel thread so safe, but I'd rather have an
> > explicit "uninterruptible, but no load-average" wait....
>
> Could you please explain why md_thread() does allow_signal(SIGKILL) ?
>
> I am just curious. It looks as if we want to allow user-space to "call"
> thread->run(), and this looks strange.

One would think that this is because md wants to be notified when system
is going to be halted/rebooted, and userspace init (whatever that is)
decides to do 'kill -9 -1' to perform the final shutdown of md (the
question is why it really should be needed, becasue all filesystems should
be R/O by that time anyway).

--
Jiri Kosina
SUSE Labs



\
 
 \ /
  Last update: 2015-05-07 15:41    [W:0.412 / U:1.856 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site