From: Shuah Khan <shuah.khan@hp.com>
To: JoonSoo Kim <js1304@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
cl@linux.com, glommer@parallels.com, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
shuahkhan@gmail.com
Subject: Re: [PATCH RESEND] mm: Restructure kmem_cache_create() to move debug cache integrity checks into a new function
Date: Mon, 06 Aug 2012 11:03:34 -0600 [thread overview]
Message-ID: <1344272614.2486.40.camel@lorien2> (raw)
In-Reply-To: <CAAmzW4Ne5pD90r+6zrrD-BXsjtf5OqaKdWY+2NSGOh1M_sWq4g@mail.gmail.com>
On Tue, 2012-08-07 at 01:49 +0900, JoonSoo Kim wrote:
> > diff --git a/mm/slab_common.c b/mm/slab_common.c
> > index 12637ce..08bc2a4 100644
> > --- a/mm/slab_common.c
> > +++ b/mm/slab_common.c
> > @@ -23,6 +23,41 @@ enum slab_state slab_state;
> > LIST_HEAD(slab_caches);
> > DEFINE_MUTEX(slab_mutex);
> >
> > +static int kmem_cache_sanity_check(const char *name, size_t size)
> > +{
> > +#ifdef CONFIG_DEBUG_VM
> > + struct kmem_cache *s = NULL;
> > +
> > + list_for_each_entry(s, &slab_caches, list) {
> > + char tmp;
> > + int res;
> > +
> > + /*
> > + * This happens when the module gets unloaded and doesn't
> > + * destroy its slab cache and no-one else reuses the vmalloc
> > + * area of the module. Print a warning.
> > + */
> > + res = probe_kernel_address(s->name, tmp);
> > + if (res) {
> > + pr_err("Slab cache with size %d has lost its name\n",
> > + s->object_size);
> > + continue;
> > + }
> > +
> > + if (!strcmp(s->name, name)) {
> > + pr_err("%s (%s): Cache name already exists.\n",
> > + __func__, name);
> > + dump_stack();
> > + s = NULL;
> > + return -EINVAL;
> > + }
> > + }
> > +
> > + WARN_ON(strchr(name, ' ')); /* It confuses parsers */
> > +#endif
> > + return 0;
> > +}
>
> As I know, following is more preferable than above.
>
> #ifdef CONFIG_DEBUG_VM
> static int kmem_cache_sanity_check(const char *name, size_t size);
> #else
> static inline int kmem_cache_sanity_check(const char *name, size_t size)
> {
> return 0;
> }
> #endif
>
> Is there any reason to do like that?
> Thanks.
No reason, just something I am used to doing :) inline is a good idea. I
can fix that easily and send v2 patch.
-- Shuah
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Shuah Khan <shuah.khan@hp.com>
To: JoonSoo Kim <js1304@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
cl@linux.com, glommer@parallels.com, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
shuahkhan@gmail.com
Subject: Re: [PATCH RESEND] mm: Restructure kmem_cache_create() to move debug cache integrity checks into a new function
Date: Mon, 06 Aug 2012 11:03:34 -0600 [thread overview]
Message-ID: <1344272614.2486.40.camel@lorien2> (raw)
In-Reply-To: <CAAmzW4Ne5pD90r+6zrrD-BXsjtf5OqaKdWY+2NSGOh1M_sWq4g@mail.gmail.com>
On Tue, 2012-08-07 at 01:49 +0900, JoonSoo Kim wrote:
> > diff --git a/mm/slab_common.c b/mm/slab_common.c
> > index 12637ce..08bc2a4 100644
> > --- a/mm/slab_common.c
> > +++ b/mm/slab_common.c
> > @@ -23,6 +23,41 @@ enum slab_state slab_state;
> > LIST_HEAD(slab_caches);
> > DEFINE_MUTEX(slab_mutex);
> >
> > +static int kmem_cache_sanity_check(const char *name, size_t size)
> > +{
> > +#ifdef CONFIG_DEBUG_VM
> > + struct kmem_cache *s = NULL;
> > +
> > + list_for_each_entry(s, &slab_caches, list) {
> > + char tmp;
> > + int res;
> > +
> > + /*
> > + * This happens when the module gets unloaded and doesn't
> > + * destroy its slab cache and no-one else reuses the vmalloc
> > + * area of the module. Print a warning.
> > + */
> > + res = probe_kernel_address(s->name, tmp);
> > + if (res) {
> > + pr_err("Slab cache with size %d has lost its name\n",
> > + s->object_size);
> > + continue;
> > + }
> > +
> > + if (!strcmp(s->name, name)) {
> > + pr_err("%s (%s): Cache name already exists.\n",
> > + __func__, name);
> > + dump_stack();
> > + s = NULL;
> > + return -EINVAL;
> > + }
> > + }
> > +
> > + WARN_ON(strchr(name, ' ')); /* It confuses parsers */
> > +#endif
> > + return 0;
> > +}
>
> As I know, following is more preferable than above.
>
> #ifdef CONFIG_DEBUG_VM
> static int kmem_cache_sanity_check(const char *name, size_t size);
> #else
> static inline int kmem_cache_sanity_check(const char *name, size_t size)
> {
> return 0;
> }
> #endif
>
> Is there any reason to do like that?
> Thanks.
No reason, just something I am used to doing :) inline is a good idea. I
can fix that easily and send v2 patch.
-- Shuah
next prev parent reply other threads:[~2012-08-06 17:03 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 23:12 [PATCH TRIVIAL] mm: Fix build warning in kmem_cache_create() Shuah Khan
2012-07-13 23:12 ` Shuah Khan
2012-07-14 9:18 ` David Rientjes
2012-07-14 9:18 ` David Rientjes
2012-07-14 12:01 ` Pekka Enberg
2012-07-14 12:01 ` Pekka Enberg
2012-07-16 3:04 ` Shuah Khan
2012-07-16 3:04 ` Shuah Khan
2012-07-16 9:58 ` David Rientjes
2012-07-16 9:58 ` David Rientjes
2012-07-16 14:17 ` Christoph Lameter
2012-07-16 14:17 ` Christoph Lameter
2012-07-16 15:56 ` Shuah Khan
2012-07-16 15:56 ` Shuah Khan
2012-07-16 19:58 ` David Rientjes
2012-07-16 19:58 ` David Rientjes
2012-07-16 20:14 ` Christoph Lameter
2012-07-16 20:14 ` Christoph Lameter
2012-07-16 23:48 ` David Rientjes
2012-07-16 23:48 ` David Rientjes
2012-07-17 14:36 ` Christoph Lameter
2012-07-17 14:36 ` Christoph Lameter
2012-07-17 14:46 ` Pekka Enberg
2012-07-17 14:46 ` Pekka Enberg
2012-07-17 15:11 ` Christoph Lameter
2012-07-17 15:11 ` Christoph Lameter
2012-07-23 7:04 ` Glauber Costa
2012-07-23 7:04 ` Glauber Costa
2012-07-25 15:28 ` Christoph Lameter
2012-07-25 15:28 ` Christoph Lameter
2012-07-17 16:52 ` Shuah Khan
2012-07-17 16:52 ` Shuah Khan
2012-07-30 10:18 ` Pekka Enberg
2012-07-30 10:18 ` Pekka Enberg
2012-07-30 19:56 ` David Rientjes
2012-07-30 19:56 ` David Rientjes
2012-07-30 20:41 ` Pekka Enberg
2012-07-30 20:41 ` Pekka Enberg
2012-07-31 2:07 ` David Rientjes
2012-07-31 2:07 ` David Rientjes
2012-07-31 6:05 ` Pekka Enberg
2012-07-31 6:05 ` Pekka Enberg
2012-08-06 3:41 ` Shuah Khan
2012-08-06 3:41 ` Shuah Khan
2012-08-06 15:14 ` [PATCH RESEND] mm: Restructure kmem_cache_create() to move debug cache integrity checks into a new function Shuah Khan
2012-08-06 15:14 ` Shuah Khan
2012-08-06 16:49 ` JoonSoo Kim
2012-08-06 16:49 ` JoonSoo Kim
2012-08-06 17:03 ` Shuah Khan [this message]
2012-08-06 17:03 ` Shuah Khan
2012-08-06 21:13 ` [PATCH v2] " Shuah Khan
2012-08-06 21:13 ` Shuah Khan
2012-08-09 14:06 ` Shuah Khan
2012-08-09 14:06 ` Shuah Khan
2012-08-09 14:13 ` Christoph Lameter (Open Source)
2012-08-09 14:13 ` Christoph Lameter (Open Source)
2012-08-09 17:01 ` Shuah Khan
2012-08-09 17:01 ` Shuah Khan
2012-08-09 19:08 ` Christoph Lameter (Open Source)
2012-08-09 19:08 ` Christoph Lameter (Open Source)
2012-08-09 19:33 ` Shuah Khan
2012-08-09 19:33 ` Shuah Khan
2012-08-12 16:40 ` [PATCH v3] " Shuah Khan
2012-08-12 16:40 ` Shuah Khan
2012-08-12 17:36 ` Christoph
2012-08-12 17:36 ` Christoph
2012-08-15 23:53 ` Andrew Morton
2012-08-15 23:53 ` Andrew Morton
2012-08-16 6:40 ` Pekka Enberg
2012-08-16 6:40 ` Pekka Enberg
2012-08-08 14:14 ` [PATCH RESEND] " Christoph Lameter (Open Source)
2012-08-08 14:14 ` Christoph Lameter (Open Source)
2012-08-08 15:13 ` Shuah Khan
2012-08-08 15:13 ` Shuah Khan
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=1344272614.2486.40.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=glommer@parallels.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=shuahkhan@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.