From: Vladimir Davydov <vdavydov@parallels.com>
To: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Dave Jones <davej@redhat.com>, Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH] slab: fix wrong retval on kmem_cache_create_memcg error path
Date: Sun, 26 Jan 2014 12:15:28 +0400 [thread overview]
Message-ID: <52E4C420.8020800@parallels.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401252036410.10325@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On 01/26/2014 08:39 AM, David Rientjes wrote:
> On Sat, 25 Jan 2014, Vladimir Davydov wrote:
>
>> diff --git a/mm/slab_common.c b/mm/slab_common.c
>> index 8e40321..499b53c 100644
>> --- a/mm/slab_common.c
>> +++ b/mm/slab_common.c
>> @@ -249,7 +249,6 @@ out_unlock:
>> name, err);
>> dump_stack();
>> }
>> - return NULL;
>> }
>> return s;
>>
>> @@ -257,6 +256,7 @@ out_free_cache:
>> memcg_free_cache_params(s);
>> kfree(s->name);
>> kmem_cache_free(kmem_cache, s);
>> + s = NULL;
>> goto out_unlock;
>> }
>>
> I thought I left spaghetti code back in my BASIC 2.0 days. It should be
> much more readable to just do
>
> diff --git a/mm/slab_common.c b/mm/slab_common.c
> --- a/mm/slab_common.c
> +++ b/mm/slab_common.c
> @@ -233,14 +233,15 @@ out_unlock:
> mutex_unlock(&slab_mutex);
> put_online_cpus();
>
> - /*
> - * There is no point in flooding logs with warnings or especially
> - * crashing the system if we fail to create a cache for a memcg. In
> - * this case we will be accounting the memcg allocation to the root
> - * cgroup until we succeed to create its own cache, but it isn't that
> - * critical.
> - */
> - if (err && !memcg) {
> + if (err) {
> + /*
> + * There is no point in flooding logs with warnings or
> + * especially crashing the system if we fail to create a cache
> + * for a memcg.
> + */
> + if (memcg)
> + return NULL;
> +
> if (flags & SLAB_PANIC)
> panic("kmem_cache_create: Failed to create slab '%s'. Error %d\n",
> name, err);
>
> and stop trying to remember what err, memcg, and s are in all possible
> contexts. Sheesh.
Hi, David,
Although it's rather a matter of personal preference, I tend to agree
with you.
Andrew,
The fix by David Rientjes is attached. It's up to you to decide, which
one looks better.
Thank you and sorry about the noise.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-slab-fix-wrong-retval-on-kmem_cache_create_memcg-err.patch --]
[-- Type: text/x-patch; name="0001-slab-fix-wrong-retval-on-kmem_cache_create_memcg-err.patch", Size: 0 bytes --]
prev parent reply other threads:[~2014-01-26 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 21:15 Vladimir Davydov
2014-01-26 4:39 ` David Rientjes
2014-01-26 8:15 ` Vladimir Davydov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E4C420.8020800@parallels.com \
--to=vdavydov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox