From: Christoph Hellwig Subject: Re: [PATCH 07/17] fs: Generic infrastructure for optional inode fields Date: Fri, 2 May 2014 07:44:09 -0700 Message-ID: <20140502144409.GB5902@infradead.org> References: <1399036808-24521-1-git-send-email-jack@suse.cz> <1399036808-24521-8-git-send-email-jack@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, Al Viro To: Jan Kara Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:48163 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751406AbaEBOoK (ORCPT ); Fri, 2 May 2014 10:44:10 -0400 Content-Disposition: inline In-Reply-To: <1399036808-24521-8-git-send-email-jack@suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, May 02, 2014 at 03:19:58PM +0200, Jan Kara wrote: > There are parts of struct inode which are used only by a few filesystems > (e.g. i_dquot pointers, i_mapping->private_list, ...). Thus all the Why don't you move the private_list into the fs inode like you did in the previous few patches and remove the references from the generic code? This would involve some heavy lifting in buffer.c, but that's long overdue anyway.