From: Ganesh Mahendran <opensource.ganesh@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
ddstreet@ieee.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm/zsmalloc: avoid unregister a NOT-registered zsmalloc zpool driver
Date: Fri, 14 Nov 2014 07:38:16 +0800 [thread overview]
Message-ID: <CADAEsF80gaDH=uctJeU7_uRBXvL4D_vX_y6Jiw71-u+uErB7ZQ@mail.gmail.com> (raw)
In-Reply-To: <20141113152247.GB1408@swordfish>
Hello
2014-11-13 23:22 GMT+08:00 Sergey Senozhatsky <sergey.senozhatsky@gmail.com>:
> On (11/13/14 21:37), Mahendran Ganesh wrote:
>> Now zsmalloc can be registered as a zpool driver into zpool when
>> CONFIG_ZPOOL is enabled. During the init of zsmalloc, when error happens,
>> we need to do cleanup. But in current code, it will unregister a not yet
>> registered zsmalloc zpool driver(*zs_zpool_driver*).
>>
>> This patch puts the cleanup in zs_init() instead of calling zs_exit()
>> where it will unregister a not-registered zpool driver.
>>
>> Signed-off-by: Mahendran Ganesh <opensource.ganesh@gmail.com>
>> ---
>> mm/zsmalloc.c | 12 ++++++++----
>> 1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
>> index 839a48c..3d2bb36 100644
>> --- a/mm/zsmalloc.c
>> +++ b/mm/zsmalloc.c
>> @@ -907,10 +907,8 @@ static int zs_init(void)
>> __register_cpu_notifier(&zs_cpu_nb);
>> for_each_online_cpu(cpu) {
>> ret = zs_cpu_notifier(NULL, CPU_UP_PREPARE, (void *)(long)cpu);
>> - if (notifier_to_errno(ret)) {
>> - cpu_notifier_register_done();
>> + if (notifier_to_errno(ret))
>> goto fail;
>> - }
>> }
>>
>> cpu_notifier_register_done();
>> @@ -920,8 +918,14 @@ static int zs_init(void)
>> #endif
>>
>> return 0;
>> +
>> fail:
>> - zs_exit();
>> + for_each_online_cpu(cpu)
>> + zs_cpu_notifier(NULL, CPU_UP_CANCELED, (void *)(long)cpu);
>> + __unregister_cpu_notifier(&zs_cpu_nb);
>> +
>> + cpu_notifier_register_done();
>> +
>> return notifier_to_errno(ret);
>
> so we duplicate same code, and there is a bit confusing part
> now: zs_cpu_notifier(CPU_UP_CANCELED) and zs_cpu_notifier(CPU_DEAD)
> calls.
Thanks for your review.
CPU_UP_CANCELED and CPU_DEAD have different scenario.
CPU_UP_CANCELED is better for fail to complete initialization. While
CPU_DEAD is better for exit(such as removing module)
Thanks.
>
> how about something like this?
>
> Factor out zsmalloc cpu notifier unregistration code and call
> it from both zs_exit() and zs_init() error path.
>
> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
>
> ---
>
> mm/zsmalloc.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> index b3b57ef..c4d2d60 100644
> --- a/mm/zsmalloc.c
> +++ b/mm/zsmalloc.c
> @@ -881,14 +881,10 @@ static struct notifier_block zs_cpu_nb = {
> .notifier_call = zs_cpu_notifier
> };
>
> -static void zs_exit(void)
> +static inline void zs_unregister_cpu_notifier()
> {
> int cpu;
>
> -#ifdef CONFIG_ZPOOL
> - zpool_unregister_driver(&zs_zpool_driver);
> -#endif
> -
> cpu_notifier_register_begin();
>
> for_each_online_cpu(cpu)
> @@ -898,6 +894,14 @@ static void zs_exit(void)
> cpu_notifier_register_done();
> }
>
> +static void zs_exit(void)
> +{
> +#ifdef CONFIG_ZPOOL
> + zpool_unregister_driver(&zs_zpool_driver);
> +#endif
> + zs_unregister_cpu_notifier();
> +}
> +
> static int zs_init(void)
> {
> int cpu, ret;
> @@ -907,10 +911,8 @@ static int zs_init(void)
> __register_cpu_notifier(&zs_cpu_nb);
> for_each_online_cpu(cpu) {
> ret = zs_cpu_notifier(NULL, CPU_UP_PREPARE, (void *)(long)cpu);
> - if (notifier_to_errno(ret)) {
> - cpu_notifier_register_done();
> + if (notifier_to_errno(ret))
> goto fail;
> - }
> }
>
> cpu_notifier_register_done();
> @@ -921,7 +923,7 @@ static int zs_init(void)
>
> return 0;
> fail:
> - zs_exit();
> + zs_unregister_cpu_notifier();
> return notifier_to_errno(ret);
> }
>
--
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>
prev parent reply other threads:[~2014-11-13 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 13:37 [PATCH 1/3] mm/zsmalloc: avoid unregister a NOT-registered zsmalloc zpool driver Mahendran Ganesh
2014-11-13 13:37 ` [PATCH 2/3] mm/zsmalloc: add __init/__exit to zs_init/zs_exit Mahendran Ganesh
2014-11-14 12:59 ` Sergey Senozhatsky
2014-11-13 13:37 ` [PATCH 3/3] mm/zsmalloc: adjust zs_init/zs_exit location Mahendran Ganesh
2014-11-13 15:22 ` [PATCH 1/3] mm/zsmalloc: avoid unregister a NOT-registered zsmalloc zpool driver Sergey Senozhatsky
2014-11-13 15:30 ` Sergey Senozhatsky
2014-11-13 22:31 ` Sergey Senozhatsky
2014-11-13 23:29 ` Minchan Kim
2014-11-13 23:38 ` Ganesh Mahendran [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='CADAEsF80gaDH=uctJeU7_uRBXvL4D_vX_y6Jiw71-u+uErB7ZQ@mail.gmail.com' \
--to=opensource.ganesh@gmail.com \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky@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;
as well as URLs for NNTP newsgroup(s).