Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752078AbbEDRfu (ORCPT ); Mon, 4 May 2015 13:35:50 -0400 Received: from mx1.redhat.com ([209.132.183.28]:44950 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751870AbbEDRfm (ORCPT ); Mon, 4 May 2015 13:35:42 -0400 Date: Mon, 4 May 2015 19:35:16 +0200 From: Oleg Nesterov To: NeilBrown Cc: Ingo Molnar , Linus Torvalds , Evgeniy Polyakov , Stephen Smalley , Alex Williamson , linux-kernel , kvm Subject: Re: [PATCH] signals: Generate warning when flush_signals() is called from non-kthread context Message-ID: <20150504173515.GA12200@redhat.com> References: <1430502057.4472.255.camel@redhat.com> <20150501193813.GA2812@gmail.com> <20150502183001.07eae212@notabene.brown> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150502183001.07eae212@notabene.brown> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 603 Lines: 17 On 05/02, NeilBrown 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. Oleg. -- 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/