From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyrill Gorcunov Subject: Re: [RFC PATCH 1/5] proc: intoduce proc_inode->pid_entry and is_tgid_pid_entry() Date: Sun, 10 Aug 2014 11:16:01 +0400 Message-ID: <20140810071601.GB14546@moon> References: <20140808185732.GA760@redhat.com> <20140808185747.GA774@redhat.com> <20140808200553.GB20553@moon> <20140809142850.GB16457@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alexander Viro , Alexey Dobriyan , Andrew Morton , David Howells , "David S. Miller" , "Eric W. Biederman" , "Kirill A. Shutemov" , Peter Zijlstra , Sasha Levin , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Oleg Nesterov Return-path: Content-Disposition: inline In-Reply-To: <20140809142850.GB16457@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Aug 09, 2014 at 04:28:50PM +0200, Oleg Nesterov wrote: > > > > Hi Oleg, sorry for not responding to previous emails, will try to review this > > things tomorrow (from a glance looks quite good!). Btw, this moment strike my > > eyes -- why don't we use kmem_cache_zalloc here but do assign nils again and > > again, maybe worth to address as well? > > Probably because this doesn't make sense to nullify proc_inode->vfs_inode, > it will be reinitialized at least by inode_init_always() anyway. Yeah, thanks. I managed to fogeth that we call inode_init_always after inode get allocated. As to series -- looks like a good start, and I think Eric is a way more confident in this area than me so i've nothing to add up to his comments.