From: Wu Bo <wubo40@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>, <cgroups@vger.kernel.org>,
<linux-block@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
"Feilong Lin" <linfeilong@huawei.com>,
Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
Zhiqiang Liu <liuzhiqiang26@huawei.com>
Subject: Re: [PATCH] blkcg: Fix memory leak in blkg_conf_prep()
Date: Mon, 18 May 2020 19:34:27 +0800 [thread overview]
Message-ID: <5cfba9c1-675d-d4e8-65bf-746712ae32e5@huawei.com> (raw)
In-Reply-To: <4c670a6c-98c3-2b14-7438-09199506d92f@web.de>
On 2020/5/15 23:08, Markus Elfring wrote:
> …
>> new_blkg = blkg_alloc(pos, q, GFP_KERNEL);
> …
>
> I suggest to omit the source code quotation from the change description.
>
>
>> if calling blkg_lookup_check() failed, at the IS_ERR block,
>> the new_blkg should be free before goto lable fail_unlock
>> in blkg_conf_prep() function.
>
> How do you think about a wording variant like the following?
>
> If a call of the function “blkg_lookup_check” failed,
> release the previously allocated block group before jumping
> to the target “fail_unlock” in the implementation of
> the function “blkg_conf_prep”.
>
Thanks for your suggestion. omit the source code quotation from the
description is more friendly. I will modify the description in V2 patch.
Thanks,
Wu Bo
>
> Would you like to add the tag “Fixes” to the commit message?
>
> Regards,
> Markus
>
prev parent reply other threads:[~2020-05-18 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 15:08 Markus Elfring
2020-05-18 11:34 ` Wu Bo [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=5cfba9c1-675d-d4e8-65bf-746712ae32e5@huawei.com \
--to=wubo40@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linfeilong@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=tj@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®