From: David Rientjes <rientjes@google.com>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Christoph Lameter <cl@gentwo.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH RESEND] slub: return correct error on slab_sysfs_init
Date: Wed, 18 Jun 2014 13:16:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1406181314290.10339@chino.kir.corp.google.com> (raw)
In-Reply-To: <53A0EB84.7030308@oracle.com>
On Wed, 18 Jun 2014, Jeff Liu wrote:
> From: Jie Liu <jeff.liu@oracle.com>
>
> Return -ENOMEM than -ENOSYS if kset_create_and_add() failed
>
Why? kset_create_and_add() can fail for a few other reasons other than
memory constraints and given that this is only done at bootstrap, it
actually seems like a duplicate name would be a bigger concern than low on
memory if another init call actually registered it.
> Signed-off-by: Jie Liu <jeff.liu@oracle.com>
> ---
> mm/slub.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index b2b0473..e10f60f 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -5301,7 +5301,7 @@ static int __init slab_sysfs_init(void)
> if (!slab_kset) {
> mutex_unlock(&slab_mutex);
> pr_err("Cannot register slab subsystem.\n");
> - return -ENOSYS;
> + return -ENOMEM;
> }
>
> slab_state = FULL;
--
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-06-18 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 1:29 Jeff Liu
2014-06-18 20:16 ` David Rientjes [this message]
2014-06-19 14:39 ` Christoph Lameter
2014-06-19 20:32 ` Andrew Morton
2014-06-19 21:34 ` David Rientjes
2014-06-20 13:51 ` Jeff Liu
2014-06-20 22:30 ` David Rientjes
2014-06-21 8:49 ` Jeff Liu
2014-06-23 13:59 ` Christoph Lameter
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.1406181314290.10339@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=cl@gentwo.org \
--cc=jeff.liu@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.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