From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756337AbcJZSeO (ORCPT ); Wed, 26 Oct 2016 14:34:14 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:41312 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752335AbcJZSeN (ORCPT ); Wed, 26 Oct 2016 14:34:13 -0400 Date: Wed, 26 Oct 2016 20:31:34 +0200 (CEST) From: Thomas Gleixner To: Oleg Nesterov cc: Andy Lutomirski , Roman Pen , Andy Lutomirski , Peter Zijlstra , Ingo Molnar , Tejun Heo , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v3 1/1] kthread: allocate kthread structure using kmalloc In-Reply-To: <20161026155155.GA28832@redhat.com> Message-ID: References: <20161025110508.9052-1-roman.penyaev@profitbricks.com> <20161025140333.GB4326@redhat.com> <20161025154301.GA12015@redhat.com> <20161026141359.GA6893@redhat.com> <20161026155155.GA28832@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: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Oct 2016, Oleg Nesterov wrote: > On 10/26, Thomas Gleixner wrote: > > > > On Wed, 26 Oct 2016, Oleg Nesterov wrote: > > > +static inline void set_kthread_struct(void *kthread) > > > +{ > > > + /* > > > + * We abuse ->set_child_tid to avoid the new member and because it > > > + * can't be wrongly copied by copy_process(). We also rely on fact > > > + * that the caller can't exec, so PF_KTHREAD can't be cleared. > > > + */ > > > + current->set_child_tid = (__force void __user *)kthread; > > > > Can we pretty please avoid this type casting? We only have 5 places using > > set_child_tid. So we can really make it a proper union > > Yes, I thought about anonymous union too, the only problem is that > it will need more comments ;) Be careful with anonymous unions. There are a few pitfalls with older compilers. That's why I said make it a proper union and fixup the 5 usage sites. It might work in this case, but you've been warned :) Thanks, tglx