Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759438Ab2HITde (ORCPT ); Thu, 9 Aug 2012 15:33:34 -0400 Received: from g4t0015.houston.hp.com ([15.201.24.18]:13484 "EHLO g4t0015.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759376Ab2HITdd (ORCPT ); Thu, 9 Aug 2012 15:33:33 -0400 Message-ID: <1344540801.2393.42.camel@lorien2> Subject: Re: [PATCH v2] mm: Restructure kmem_cache_create() to move debug cache integrity checks into a new function From: Shuah Khan Reply-To: shuah.khan@hp.com To: "Christoph Lameter (Open Source)" Cc: penberg@kernel.org, glommer@parallels.com, js1304@gmail.com, David Rientjes , linux-mm@kvack.org, LKML , Andrew Morton , Linus Torvalds , shuah.khan@hp.com Date: Thu, 09 Aug 2012 13:33:21 -0600 In-Reply-To: References: <1342221125.17464.8.camel@lorien2> <1344224494.3053.5.camel@lorien2> <1344266096.2486.17.camel@lorien2> <1344272614.2486.40.camel@lorien2> <1344287631.2486.57.camel@lorien2> <1344531695.2393.27.camel@lorien2> Organization: ISS-Linux Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 39 On Thu, 2012-08-09 at 14:08 -0500, Christoph Lameter (Open Source) wrote: > On Thu, 9 Aug 2012, Shuah Khan wrote: > > > Moving these checks into kmem_cache_sanity_check() would mean return > > path handling will change. The first block of sanity checks for name, > > and size etc. are done before holding the slab_mutex and the second > > block that checks the slab lists is done after holding the mutex. > > Depending on which one fails, return handling is going to be different > > in that if second block fails, mutex needs to be unlocked and when the > > first block fails, there is no need to do that. Nothing that is too > > complex to solve, just something that needs to be handled. > > Right. The taking of the mutex etc is not depending on the parameters at > all. So its possible. Its rather simple. > > > Comments, thoughts on > > > > 1. just remove size from kmem_cache_sanity_check() parameters > > or > > 2. move first block sanity checks into kmem_cache_sanity_check() > > > > Personally I prefer the first option to avoid complexity in return path > > handling. Would like to hear what others think. > > We already have to deal with the return path handling for other failure > cases. Thanks for the feedback. I will send v3 patch with the changes we discussed. -- Shuah -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/