public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Ying Huang <huang.ying.caritas@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH] resource: Fix resource leak in get_free_mem_region()
Date: Tue, 4 Mar 2025 09:44:38 +0000	[thread overview]
Message-ID: <7e01507e-deb2-4acb-a2b7-530beb0d92dc@fujitsu.com> (raw)
In-Reply-To: <20250304092219.GH3713119@black.fi.intel.com>



On 04/03/2025 17:22, Mika Westerberg wrote:
> On Tue, Mar 04, 2025 at 12:34:15PM +0800, Li Zhijian wrote:
>> The leak is detected by the kernel memory leak detector (`kmemleak`)
>> following a `cxl create-region` failure:
>>
>>   cxl_acpi ACPI0017:00: decoder0.0: created region2
>>   cxl region2: HPA allocation error (-34) for size:0x0000000100000000 in CXL Window 0 [mem 0xa90000000-0x1a8fffffff flags 0x200]
>>   kmemleak: 1 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
>>
>>      __kmalloc_cache_noprof+0x28c/0x350
>>      get_free_mem_region+0x45/0x380
>>      alloc_free_mem_region+0x1d/0x30
>>      size_store+0x180/0x290 [cxl_core]
>>      kernfs_fop_write_iter+0x13f/0x1e0
>>      vfs_write+0x37c/0x540
>>      ksys_write+0x68/0xe0
>>      do_syscall_64+0x6e/0x190
>>      entry_SYSCALL_64_after_hwframe+0x76/0x7e
>>
>> Fixes: 14b80582c43e ("resource: Introduce alloc_free_mem_region()")
>> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
>> ---
>>   kernel/resource.c | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/kernel/resource.c b/kernel/resource.c
>> index 12004452d999..aa0b1da143eb 100644
>> --- a/kernel/resource.c
>> +++ b/kernel/resource.c
>> @@ -2000,6 +2000,8 @@ get_free_mem_region(struct device *dev, struct resource *base,
>>   		devres_free(dr);
>>   	} else if (dev)
>>   		devm_release_action(dev, remove_free_mem_region, res);
>> +	else
>> +		free_resource(res);
> 
> It should use {} as per coding style:


The script/checkpatch.pl is happy with both of these 2 styles in practice.

Thanks
Zhijian

> 
> 	} else {
> 		free_resource(res);
> 	}
> 
> (probably should add that to the previous branch too).

  reply	other threads:[~2025-03-04  9:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04  4:34 [PATCH] resource: Fix resource leak in get_free_mem_region() Li Zhijian
2025-03-04  9:22 ` Mika Westerberg
2025-03-04  9:44   ` Zhijian Li (Fujitsu) [this message]
2025-03-04 10:03     ` Mika Westerberg
2025-03-04 12:09 ` Andy Shevchenko
2025-03-04 23:43 ` Dan Williams

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=7e01507e-deb2-4acb-a2b7-530beb0d92dc@fujitsu.com \
    --to=lizhijian@fujitsu.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=huang.ying.caritas@gmail.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.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