mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Clément Léger" <cleger@rivosinc.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Charlie Jenkins <charlie@rivosinc.com>,
	zhangkai@iscas.ac.cn
Subject: Re: [PATCH] riscv: module: use a plain variable for list_head instead of a pointer
Date: Wed, 27 Nov 2024 15:18:25 +0100	[thread overview]
Message-ID: <2a902c69-1115-451d-82b7-dcf7641a7c4b@rivosinc.com> (raw)
In-Reply-To: <20241127-2c074e38cc599c7e2d0da505@orel>



On 27/11/2024 15:02, Andrew Jones wrote:
> On Wed, Nov 27, 2024 at 11:30:14AM +0100, Clément Léger wrote:
>> list_head does not need to be allocated, it can be a plain variable.
> 
> rel_head's list_head member, rel_entry, doesn't need to be allocated,
> its storage can just be part of the allocated rel_head.
> 
>> Remove the pointer which allows to get rid of the allocation as well as
>> an existing memory leak.
> 
> It'd be nice to add how the memory leak was found. Inspection or some
> tool?

Yeah sure, it was actually found by Kai Zang, I have added him as Cc but
I can surely give him credit for finding the memleak, I'll add him with
a Reported-by.

Thanks,

Clément

> 
>>
>> Signed-off-by: Clément Léger <cleger@rivosinc.com>
>>
>> ---
>>  arch/riscv/kernel/module.c | 18 ++++--------------
>>  1 file changed, 4 insertions(+), 14 deletions(-)
>>
>> diff --git a/arch/riscv/kernel/module.c b/arch/riscv/kernel/module.c
>> index 1cd461f3d872..47d0ebeec93c 100644
>> --- a/arch/riscv/kernel/module.c
>> +++ b/arch/riscv/kernel/module.c
>> @@ -23,7 +23,7 @@ struct used_bucket {
>>  
>>  struct relocation_head {
>>  	struct hlist_node node;
>> -	struct list_head *rel_entry;
>> +	struct list_head rel_entry;
>>  	void *location;
>>  };
>>  
>> @@ -634,7 +634,7 @@ process_accumulated_relocations(struct module *me,
>>  			location = rel_head_iter->location;
>>  			list_for_each_entry_safe(rel_entry_iter,
>>  						 rel_entry_iter_tmp,
>> -						 rel_head_iter->rel_entry,
>> +						 &rel_head_iter->rel_entry,
>>  						 head) {
>>  				curr_type = rel_entry_iter->type;
>>  				reloc_handlers[curr_type].reloc_handler(
>> @@ -704,16 +704,7 @@ static int add_relocation_to_accumulate(struct module *me, int type,
>>  			return -ENOMEM;
>>  		}
>>  
>> -		rel_head->rel_entry =
>> -			kmalloc(sizeof(struct list_head), GFP_KERNEL);
>> -
>> -		if (!rel_head->rel_entry) {
>> -			kfree(entry);
>> -			kfree(rel_head);
>> -			return -ENOMEM;
>> -		}
>> -
>> -		INIT_LIST_HEAD(rel_head->rel_entry);
>> +		INIT_LIST_HEAD(&rel_head->rel_entry);
>>  		rel_head->location = location;
>>  		INIT_HLIST_NODE(&rel_head->node);
>>  		if (!current_head->first) {
>> @@ -722,7 +713,6 @@ static int add_relocation_to_accumulate(struct module *me, int type,
>>  
>>  			if (!bucket) {
>>  				kfree(entry);
>> -				kfree(rel_head->rel_entry);
>>  				kfree(rel_head);
>>  				return -ENOMEM;
>>  			}
>> @@ -735,7 +725,7 @@ static int add_relocation_to_accumulate(struct module *me, int type,
>>  	}
>>  
>>  	/* Add relocation to head of discovered rel_head */
>> -	list_add_tail(&entry->head, rel_head->rel_entry);
>> +	list_add_tail(&entry->head, &rel_head->rel_entry);
>>  
>>  	return 0;
>>  }
>> -- 
>> 2.45.2
>>
>>
> 
> Other than the commit message change suggestions,
> 
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>


      reply	other threads:[~2024-11-27 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 10:30 Clément Léger
2024-11-27 14:02 ` Andrew Jones
2024-11-27 14:18   ` Clément Léger [this message]

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=2a902c69-1115-451d-82b7-dcf7641a7c4b@rivosinc.com \
    --to=cleger@rivosinc.com \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=zhangkai@iscas.ac.cn \
    /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®