mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Konstantin Meskhidze <konstantin.meskhidze@huawei.com>,
	<dan.j.williams@intel.com>
Cc: <vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
	<nvdimm@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<yusongping@huawei.com>, <artem.kuzin@huawei.com>
Subject: Re: [PATCH] drivers: nvdimm: fix dereference after free
Date: Thu, 17 Aug 2023 09:04:45 -0700	[thread overview]
Message-ID: <0744195e-181f-2e96-b18b-98c39985cfcc@intel.com> (raw)
In-Reply-To: <cb36ebb0-6220-c3d9-0772-bfcbd16baa77@intel.com>



On 8/17/23 08:45, Dave Jiang wrote:
> 
> 
> On 8/17/23 04:41, Konstantin Meskhidze wrote:
>> 'nd_pmu->pmu.attr_groups' is dereferenced in function
>> 'nvdimm_pmu_free_hotplug_memory' call after it has been freed. Because in
>> function 'nvdimm_pmu_free_hotplug_memory' memory pointed by the fields of
>> 'nd_pmu->pmu.attr_groups' is deallocated it is necessary to call 'kfree'
>> after 'nvdimm_pmu_free_hotplug_memory'.
>>
>> Co-developed-by: Ivanov Mikhail <ivanov.mikhail1@huawei-partners.com>
>> Signed-off-by: Konstantin Meskhidze <konstantin.meskhidze@huawei.com>
> 
> LGTM
> 
> Does this need a Fixes tag?

Applied. Modified subject to "nvdimm: Fix dereference after free in 
register_nvdimm_pmu()"

Also added Fixes tag:
Fixes: 0fab1ba6ad6b ("drivers/nvdimm: Add perf interface to expose 
nvdimm performance stats")


> 
>> ---
>>   drivers/nvdimm/nd_perf.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/nvdimm/nd_perf.c b/drivers/nvdimm/nd_perf.c
>> index 14881c4e0..2b6dc80d8 100644
>> --- a/drivers/nvdimm/nd_perf.c
>> +++ b/drivers/nvdimm/nd_perf.c
>> @@ -307,10 +307,10 @@ int register_nvdimm_pmu(struct nvdimm_pmu 
>> *nd_pmu, struct platform_device *pdev)
>>       }
>>       rc = perf_pmu_register(&nd_pmu->pmu, nd_pmu->pmu.name, -1);
>>       if (rc) {
>> -        kfree(nd_pmu->pmu.attr_groups);
>>           nvdimm_pmu_free_hotplug_memory(nd_pmu);
>> +        kfree(nd_pmu->pmu.attr_groups);
>>           return rc;
>>       }
>>       pr_info("%s NVDIMM performance monitor support registered\n",
> 

  reply	other threads:[~2023-08-17 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 11:41 Konstantin Meskhidze
2023-08-17 14:31 ` Jeff Moyer
2023-08-17 15:45 ` Dave Jiang
2023-08-17 16:04   ` Dave Jiang [this message]
2023-08-17 15:51 ` 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=0744195e-181f-2e96-b18b-98c39985cfcc@intel.com \
    --to=dave.jiang@intel.com \
    --cc=artem.kuzin@huawei.com \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=konstantin.meskhidze@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=vishal.l.verma@intel.com \
    --cc=yusongping@huawei.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

all inboxes | Powered by JetHome®