From: Al Viro Subject: Re: [PATCH v12 05/18] fs: do not use destroy_super() in alloc_super() fail path Date: Tue, 3 Dec 2013 13:37:55 +0000 Message-ID: <20131203133755.GJ10323@ZenIV.linux.org.uk> References: <20131203090041.GB8803@dastard> <529DA2F5.1040602@parallels.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <529DA2F5.1040602@parallels.com> Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Vladimir Davydov Cc: Dave Chinner , hannes@cmpxchg.org, mhocko@suse.cz, dchinner@redhat.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, devel@openvz.org, glommer@openvz.org On Tue, Dec 03, 2013 at 01:23:01PM +0400, Vladimir Davydov wrote: > Actually, I'm not going to modify the list_lru structure, because I > think it's good as it is. I'd like to substitute it with a new > structure, memcg_list_lru, only in those places where this functionality > (per-memcg scanning) is really needed. This new structure would look > like this: > > struct memcg_list_lru { > struct list_lru global_lru; > struct list_lru **memcg_lrus; > struct list_head list; > void *old_lrus; > } > > Since old_lrus and memcg_lrus can be NULL under normal operation, in > memcg_list_lru_destroy() I'd have to check either the list or the > global_lru field, i.e. it would look like: > > if (!list.next) > /* has not been initialized */ > return; > > or ... or just use hlist_head. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org