From: Coly Li <i@coly.li>
To: Liang Chen <liangchen.linux@gmail.com>, linux-bcache@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, colyli@suse.de, bcache@linux.ewheeler.net
Subject: Re: [PATCH] bcache: explicitly destory mutex while exiting
Date: Thu, 4 May 2017 21:59:41 +0800 [thread overview]
Message-ID: <823fcdcf-893e-edc7-62c2-585db7f868ed@coly.li> (raw)
In-Reply-To: <1493712595-21528-1-git-send-email-liangchen.linux@gmail.com>
On 2017/5/2 下午4:09, Liang Chen wrote:
> mutex_destroy does nothing most of time, but it's better to call
> it to make the code future proof and it also has some meaning
> for like mutex debug.
>
Hi Liang,
Could you please explain a little bit more about how mutex_destroy()
helps to future proof of the code, and how it helps to mutex debug ?
Forgive me for not catching your point.
Thanks.
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
> ---
> drivers/md/bcache/super.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/md/bcache/super.c b/drivers/md/bcache/super.c
> index 85e3f21..406fe03 100644
> --- a/drivers/md/bcache/super.c
> +++ b/drivers/md/bcache/super.c
> @@ -2083,6 +2083,7 @@ static void bcache_exit(void)
> if (bcache_major)
> unregister_blkdev(bcache_major, "bcache");
> unregister_reboot_notifier(&reboot);
> + mutex_destroy(&bch_register_lock);
> }
>
> static int __init bcache_init(void)
> @@ -2100,6 +2101,7 @@ static int __init bcache_init(void)
>
> bcache_major = register_blkdev(0, "bcache");
> if (bcache_major < 0) {
> + mutex_destroy(&bch_register_lock);
> unregister_reboot_notifier(&reboot);
> return bcache_major;
> }
>
--
Coly Li
prev parent reply other threads:[~2017-05-04 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 8:09 Liang Chen
2017-05-04 13:59 ` Coly Li [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=823fcdcf-893e-edc7-62c2-585db7f868ed@coly.li \
--to=i@coly.li \
--cc=bcache@linux.ewheeler.net \
--cc=colyli@suse.de \
--cc=liangchen.linux@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®