From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Mahendran Ganesh <opensource.ganesh@gmail.com>,
Nitin Gupta <ngupta@vflare.org>,
linux-mm@kvack.or, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zsmalloc: fix zs_init cpu notifier error handling
Date: Wed, 19 Nov 2014 22:14:33 +0900 [thread overview]
Message-ID: <20141119131433.GA1003@swordfish> (raw)
In-Reply-To: <20141118141212.07b64fdd2f32e8d3b0f725cb@linux-foundation.org>
On (11/18/14 14:12), Andrew Morton wrote:
> > Mahendran Ganesh reported that zpool-enabled zsmalloc should not
> > call zpool_unregister_driver() from zs_init() if cpu notifier
> > registration has failed, because error handling is performed
> > before we register the driver via zpool_register_driver() call.
> >
> > Factor out cpu notifier registration and unregistration code and
> > fix zs_init() error handling.
>
>
> So we can now do this, yes?
yes, sir.
I didn't do this because I though Mahendran would resend his
patch.
thank you.
-ss
>
> --- a/mm/zsmalloc.c~mm-zsmallocc-use-__init-and-__exit
> +++ a/mm/zsmalloc.c
> @@ -911,7 +911,7 @@ static int zs_register_cpu_notifier(void
> return notifier_to_errno(ret);
> }
>
> -static void zs_exit(void)
> +static void __exit zs_exit(void)
> {
> #ifdef CONFIG_ZPOOL
> zpool_unregister_driver(&zs_zpool_driver);
> @@ -919,7 +919,7 @@ static void zs_exit(void)
> zs_unregister_cpu_notifier();
> }
>
> -static int zs_init(void)
> +static int __init zs_init(void)
> {
> int ret = zs_register_cpu_notifier();
>
>
prev parent reply other threads:[~2014-11-19 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 12:57 [PATCH] zsmalloc: fix zs_init cpu notifier error handling Sergey Senozhatsky
2014-11-18 22:12 ` Andrew Morton
2014-11-19 13:14 ` Sergey Senozhatsky [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=20141119131433.GA1003@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.or \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=opensource.ganesh@gmail.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