From: Dave Jiang <dave.jiang@intel.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
Ira Weiny <ira.weiny@intel.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"jonathan.cameron@huawei.com" <jonathan.cameron@huawei.com>,
"alison.schofield@intel.com" <alison.schofield@intel.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxl/region: Fix memregion leaks in devm_cxl_add_region()
Date: Tue, 7 May 2024 08:52:53 -0700 [thread overview]
Message-ID: <0a086052-5ed0-4b5f-b676-338662c2dbea@intel.com> (raw)
In-Reply-To: <0782e741-5478-4b62-866e-f966ab5cad91@fujitsu.com>
On 5/6/24 7:42 PM, Zhijian Li (Fujitsu) wrote:
>
>
> On 30/04/2024 00:23, Ira Weiny wrote:
>> Li Zhijian wrote:
>>> Move memregion_free(id) out of cxl_region_alloc() and
>>> explicately free memregion in devm_cxl_add_region() error path.
>> ^^^^
>> explicitly
>>
>> BTW you should run checkpatch.pl which will check spelling.
>
>
> I remember I've done this check, but it seems the it doesn't work for me.
> Did I miss something?
>
> $ ./scripts/checkpatch.pl 0001-cxl-region-Fix-memregion-leaks-in-devm_cxl_add_regio.patch
> total: 0 errors, 0 warnings, 23 lines checked
>
> 0001-cxl-region-Fix-memregion-leaks-in-devm_cxl_add_regio.patch has no obvious style problems and is ready for submission.
Pass in --codespell parameter. And make sure you have the codespell dictionary installed (i.e. /usr/share/codespell/dictionary.txt).
DJ
>
>
>
>>
>> I'm not following what the problem is you are trying to fix. This seems
>> like it just moves the memregion_free() around a bit but the logic is the
>> same.
>>
>
> Sorry, I think my commit log may be misleading. In fact, this patch mainly fixes
> the memregion leak in devm_cxl_add_region() when it gets an invalid mode.
>
>>> default:
>>> dev_err(&cxlrd->cxlsd.cxld.dev, "unsupported mode %d\n", mode);
>>> + memregion_free(id);
>>> return ERR_PTR(-EINVAL);
>>> }
>
> Additionally, to maintain consistent error handling, I also moved memregion_free(id) from
> cxl_region_alloc() to devm_cxl_add_region() so that devm_cxl_add_region() can
> free memregion explicitly in error path.
>
>
> Thanks
> Zhijian
>
>
>> Ira
>>
>>>
>>> After cxl_region_alloc() succeed, memregion will be freed by
>>> cxl_region_type.release()
>>>
>>> Fixes: 6e099264185d ("cxl/region: Add volatile region creation support")
>>> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
>>> ---
>>> drivers/cxl/core/region.c | 9 +++++----
>>> 1 file changed, 5 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
>>> index 812b2948b6c6..8535718a20f0 100644
>>> --- a/drivers/cxl/core/region.c
>>> +++ b/drivers/cxl/core/region.c
>>> @@ -2250,10 +2250,8 @@ static struct cxl_region *cxl_region_alloc(struct cxl_root_decoder *cxlrd, int i
>>> struct device *dev;
>>>
>>> cxlr = kzalloc(sizeof(*cxlr), GFP_KERNEL);
>>> - if (!cxlr) {
>>> - memregion_free(id);
>>> + if (!cxlr)
>>> return ERR_PTR(-ENOMEM);
>>> - }
>>>
>>> dev = &cxlr->dev;
>>> device_initialize(dev);
>>> @@ -2358,12 +2356,15 @@ static struct cxl_region *devm_cxl_add_region(struct cxl_root_decoder *cxlrd,
>>> break;
>>> default:
>>> dev_err(&cxlrd->cxlsd.cxld.dev, "unsupported mode %d\n", mode);
>>> + memregion_free(id);
>>> return ERR_PTR(-EINVAL);
>>> }
>>>
>>> cxlr = cxl_region_alloc(cxlrd, id);
>>> - if (IS_ERR(cxlr))
>>> + if (IS_ERR(cxlr)) {
>>> + memregion_free(id);
>>> return cxlr;
>>> + }
>>> cxlr->mode = mode;
>>> cxlr->type = type;
>>>
>>> --
>>> 2.29.2
>>>
>>
>>
next prev parent reply other threads:[~2024-05-07 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 5:37 [PATCH] cxl/region: Fix memregion leaks in devm_cxl_add_region() Li Zhijian
2024-04-29 16:23 ` Ira Weiny
[not found] ` <TY1PR01MB1562E0A5EA4F95FFE0F39602A51F2@TY1PR01MB1562.jpnprd01.prod.outlook.com>
2024-05-03 16:07 ` Dan Williams
2024-05-07 5:28 ` Zhijian Li (Fujitsu)
2024-05-07 2:42 ` Zhijian Li (Fujitsu)
2024-05-07 15:52 ` Dave Jiang [this message]
2024-05-09 3:11 ` Zhijian Li (Fujitsu)
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=0a086052-5ed0-4b5f-b676-338662c2dbea@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=vishal.l.verma@intel.com \
/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