From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, wency@cn.fujitsu.com, toshi.kani@hp.com
Subject: Re: [PATCH] firmware, memmap: fix firmware_map_entry leak
Date: Tue, 16 Apr 2013 08:37:07 +0900 [thread overview]
Message-ID: <516C8F23.7050209@jp.fujitsu.com> (raw)
In-Reply-To: <516BC25B.9090708@cn.fujitsu.com>
2013/04/15 18:03, Tang Chen wrote:
>
> Reviewed-by: Tang Chen <tangchen@cn.fujitsu.com>
Thank you for your review.
Thanks,
Yasuaki Ishimatsu
>
> Thanks. :)
>
> On 04/15/2013 01:48 PM, Yasuaki Ishimatsu wrote:
>> When hot removing a memory, a firmware_map_entry which has memory range
>> of the memory is released by release_firmware_map_entry(). If the entry
>> is allocated by bootmem, release_firmware_map_entry() adds the entry to
>> map_entires_bootmem list when firmware_map_find_entry() finds the entry
>> from map_entries list. But firmware_map_find_entry never find the entry
>> sicne map_entires list does not have the entry. So the entry just leaks.
>>
>> Here are steps of leaking firmware_map_entry:
>> firmware_map_remove()
>> -> firmware_map_find_entry()
>> Find released entry from map_entries list
>> -> firmware_map_remove_entry()
>> Delete the entry from map_entries list
>> -> remove_sysfs_fw_map_entry()
>> ...
>> -> release_firmware_map_entry()
>> -> firmware_map_find_entry()
>> Find the entry from map_entries list but the entry has been
>> deleted from map_entries list. So the entry is not added
>> to map_entries_bootmem. Thus the entry leaks
>>
>> release_firmware_map_entry() should not call firmware_map_find_entry()
>> since releaed entry has been deleted from map_entries list.
>> So the patch delete firmware_map_find_entry() from releae_firmware_map_entry()
>>
>> Signed-off-by: Yasuaki Ishimatsu<isimatu.yasuaki@jp.fujitsu.com>
>> ---
>> drivers/firmware/memmap.c | 9 +++------
>> 1 files changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/firmware/memmap.c b/drivers/firmware/memmap.c
>> index 0b5b5f6..e2e04b0 100644
>> --- a/drivers/firmware/memmap.c
>> +++ b/drivers/firmware/memmap.c
>> @@ -114,12 +114,9 @@ static void __meminit release_firmware_map_entry(struct kobject *kobj)
>> * map_entries_bootmem here, and deleted from&map_entries in
>> * firmware_map_remove_entry().
>> */
>> - if (firmware_map_find_entry(entry->start, entry->end,
>> - entry->type)) {
>> - spin_lock(&map_entries_bootmem_lock);
>> - list_add(&entry->list,&map_entries_bootmem);
>> - spin_unlock(&map_entries_bootmem_lock);
>> - }
>> + spin_lock(&map_entries_bootmem_lock);
>> + list_add(&entry->list,&map_entries_bootmem);
>> + spin_unlock(&map_entries_bootmem_lock);
>>
>> return;
>> }
>>
>>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-15 23:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 5:48 Yasuaki Ishimatsu
2013-04-15 7:04 ` Wanpeng Li
2013-04-15 7:24 ` Yasuaki Ishimatsu
2013-04-15 7:04 ` Wanpeng Li
2013-04-15 9:03 ` Tang Chen
2013-04-15 23:37 ` Yasuaki Ishimatsu [this message]
2013-04-15 21:00 ` Toshi Kani
2013-04-15 23:38 ` Yasuaki Ishimatsu
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=516C8F23.7050209@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tangchen@cn.fujitsu.com \
--cc=toshi.kani@hp.com \
--cc=wency@cn.fujitsu.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