From: David Rientjes <rientjes@google.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Christoph Lameter <cl@linux.com>,
Jonathan Brassow <jbrassow@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, dm-devel@redhat.com
Subject: Re: [PATCH] slab_common: fix the check for duplicate slab names
Date: Tue, 4 Mar 2014 14:48:31 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1403041448190.5421@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1403041711300.29476@file01.intranet.prod.int.rdu2.redhat.com>
On Tue, 4 Mar 2014, Mikulas Patocka wrote:
> The patch 3e374919b314f20e2a04f641ebc1093d758f66a4 is supposed to fix the
> problem where kmem_cache_create incorrectly reports duplicate cache name
> and fails. The problem is described in the header of that patch.
>
> However, the patch doesn't really fix the problem because of these
> reasons:
>
> * the logic to test for debugging is reversed. It was intended to perform
> the check only if slub debugging is enabled (which implies that caches
> with the same parameters are not merged). Therefore, there should be
> #if !defined(CONFIG_SLUB) || defined(CONFIG_SLUB_DEBUG_ON)
> The current code has the condition reversed and performs the test if
> debugging is disabled.
>
> * slub debugging may be enabled or disabled based on kernel command line,
> CONFIG_SLUB_DEBUG_ON is just the default settings. Therefore the test
> based on definition of CONFIG_SLUB_DEBUG_ON is unreliable.
>
> This patch fixes the problem by removing the test
> "!defined(CONFIG_SLUB_DEBUG_ON)". Therefore, duplicate names are never
> checked if the SLUB allocator is used.
>
> Note to stable kernel maintainers: when backporint this patch, please
> backport also the patch 3e374919b314f20e2a04f641ebc1093d758f66a4.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Acked-by: David Rientjes <rientjes@google.com>
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-04 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 22:13 Mikulas Patocka
2014-03-04 22:48 ` David Rientjes [this message]
2014-03-25 17:03 ` Mike Snitzer
2014-03-25 18:07 ` Christoph Lameter
2014-05-23 20:16 ` Mike Snitzer
2014-05-23 21:28 ` Pekka Enberg
2014-05-24 0:37 ` Mike Snitzer
2014-07-22 22:14 ` Mike Snitzer
2014-07-22 22:41 ` [patch] " David Rientjes
2014-07-22 22:58 ` [git pull] stable mm/slab_common.c fix for 3.16-rc7 Mike Snitzer
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=alpine.DEB.2.02.1403041448190.5421@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=agk@redhat.com \
--cc=cl@linux.com \
--cc=dm-devel@redhat.com \
--cc=jbrassow@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mpatocka@redhat.com \
--cc=penberg@kernel.org \
/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