From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S942620AbcJ1Svj (ORCPT <rfc822;w@1wt.eu>);
        Fri, 28 Oct 2016 14:51:39 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:48139 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S935899AbcJ1Svi (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 28 Oct 2016 14:51:38 -0400
Date: Fri, 28 Oct 2016 20:48:54 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Oleg Nesterov <oleg@redhat.com>
cc: Andy Lutomirski <luto@amacapital.net>,
        Roman Pen <roman.penyaev@profitbricks.com>,
        Andy Lutomirski <luto@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>,
        Tejun Heo <tj@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] kthread: make struct kthread kmalloc'ed
In-Reply-To: <20161028161138.GB8933@redhat.com>
Message-ID: <alpine.DEB.2.20.1610282046500.5053@nanos>
References: <20161025110508.9052-1-roman.penyaev@profitbricks.com> <20161025140333.GB4326@redhat.com> <20161025154301.GA12015@redhat.com> <CALCETrVmczve=knhYGrcXkeAXRQR_oY4ac2BSc7V0TEnx6-GFA@mail.gmail.com> <20161026141359.GA6893@redhat.com>
 <alpine.DEB.2.20.1610261650260.4983@nanos> <20161026155155.GA28832@redhat.com> <alpine.DEB.2.20.1610262027110.5013@nanos> <20161028161106.GA8933@redhat.com> <20161028161138.GB8933@redhat.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 28 Oct 2016, Oleg Nesterov wrote:

> I still think we should kill struct kthread in its current form, but this
> needs cleanups outside of kthread.c.
> 
> So make it kmalloc'ed for now to avoid the problems with stack corruption,
> for example the crashed kthread will likely OOPS again because its .exited
> was destroyed by rewind_stack_do_exit().
> 
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>

Reviewed-by: Thomas Gleixner <tglx@linutronix.de>