From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: shli@kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed").
Date: Mon, 12 Sep 2016 21:09:48 +0200 [thread overview]
Message-ID: <752ab1d9-412a-149b-a241-e604040ebaff@wanadoo.fr> (raw)
Hi,
I'm puzzled by commit f9a67b1182e5 ("md/bitmap: clear bitmap if
bitmap_create failed").
Part of the commit is:
@@ -1865,8 +1866,10 @@ int bitmap_copy_from_slot(struct mddev *mddev,
int slot,
struct bitmap_counts *counts;
struct bitmap *bitmap = bitmap_create(mddev, slot);
- if (IS_ERR(bitmap))
+ if (IS_ERR(bitmap)) {
+ bitmap_free(bitmap);
return PTR_ERR(bitmap);
+ }
but if 'bitmap' is an error, I think that bad things will happen in
'bitmap_free()' when, at the beginning of the function, we will execute:
if (bitmap->sysfs_can_clear) <-----------------
sysfs_put(bitmap->sysfs_can_clear);
However, the commit log message is really explicit and adding this call
to 'bitmap_free' has really been done one purpose. ("If bitmap_create
returns an error, we need to call either bitmap_destroy or bitmap_free
to do clean up, ...")
It is also not consistent with the comment before function bitmap_create():
* if this returns an error, bitmap_destroy must be called to do
clean up
* once mddev->bitmap is set
I may have missed something, but I don't see what.
Is this commit correct?
Best regards,
CJ
next reply other threads:[~2016-09-12 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 19:09 Christophe JAILLET [this message]
2016-09-13 17:24 ` Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed") Shaohua Li
2016-09-14 8:25 ` Guoqing Jiang
2016-09-14 20:39 ` Marion & Christophe JAILLET
2016-09-18 9:19 ` Guoqing Jiang
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=752ab1d9-412a-149b-a241-e604040ebaff@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@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