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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
