From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 7 Nov 2016 14:26:08 -0800 From: Andrew Morton To: Andrey Ryabinin Cc: Alexander Viro , Tejun Heo , "Rafael J. Wysocki" , Pavel Machek , "Oleg Nesterov" , , , , Subject: Re: [PATCH] coredump: fix unfreezable coredumping task Message-Id: <20161107142608.e4fa032b2e32b623663ff2e9@linux-foundation.org> In-Reply-To: <1475225434-3753-1-git-send-email-aryabinin@virtuozzo.com> References: <1475225434-3753-1-git-send-email-aryabinin@virtuozzo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, 30 Sep 2016 11:50:34 +0300 Andrey Ryabinin wrote: > It could be not possible to freeze coredumping task when it waits > for 'core_state->startup' completion, because threads are frozen > in get_signal() before they got a chance to complete 'core_state->startup'. > > Use freezer_do_not_count() to tell freezer to ignore coredumping > task while it waits for core_state->startup completion. > > Signed-off-by: Andrey Ryabinin > Cc: stable@vger.kernel.org The changelog provides no reason why this patch should be merged into -stable. Nor into anything else, really. Please (as always) provide a full description of the bug's end-user visible effects.