Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1634231 > unrolled thread

[PATCH] bcache: explicitly destory mutex while exiting

Started byLiang Chen <liangchen.linux@gmail.com>
First post2017-05-02 10:20 +0200
Last post2017-05-04 16:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] bcache: explicitly destory mutex while exiting Liang Chen <liangchen.linux@gmail.com> - 2017-05-02 10:20 +0200
    Re: [PATCH] bcache: explicitly destory mutex while exiting Coly Li <i@coly.li> - 2017-05-04 16:20 +0200

#1634231 — [PATCH] bcache: explicitly destory mutex while exiting

FromLiang Chen <liangchen.linux@gmail.com>
Date2017-05-02 10:20 +0200
Subject[PATCH] bcache: explicitly destory mutex while exiting
Message-ID<tCBcm-421-33@gated-at.bofh.it>
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.

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;
 	}
-- 
1.8.3.1

[toc] | [next] | [standalone]


#1635772

FromColy Li <i@coly.li>
Date2017-05-04 16:20 +0200
Message-ID<tDpLQ-4yP-21@gated-at.bofh.it>
In reply to#1634231
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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web