[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c670a6c-98c3-2b14-7438-09199506d92f@web.de>
Date: Fri, 15 May 2020 17:08:24 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Wu Bo <wubo40@...wei.com>, cgroups@...r.kernel.org,
linux-block@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Feilong Lin <linfeilong@...wei.com>,
Jens Axboe <axboe@...nel.dk>, Tejun Heo <tj@...nel.org>,
Zhiqiang Liu <liuzhiqiang26@...wei.com>
Subject: Re: [PATCH] blkcg: Fix memory leak in blkg_conf_prep()
…
> 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”.
Would you like to add the tag “Fixes” to the commit message?
Regards,
Markus
Powered by blists - more mailing lists