[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161107142608.e4fa032b2e32b623663ff2e9@linux-foundation.org>
Date: Mon, 7 Nov 2016 14:26:08 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andrey Ryabinin <aryabinin@...tuozzo.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Tejun Heo <tj@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>, "Oleg Nesterov" <oleg@...hat.com>,
<linux-pm@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>
Subject: Re: [PATCH] coredump: fix unfreezable coredumping task
On Fri, 30 Sep 2016 11:50:34 +0300 Andrey Ryabinin <aryabinin@...tuozzo.com> 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 <aryabinin@...tuozzo.com>
> Cc: stable@...r.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.
Powered by blists - more mailing lists