linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: liuye <liuye@kylinos.cn>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Liam.Howlett@oracle.com, lorenzo.stoakes@oracle.com,
	jannh@google.com, vbabka@suse.cz, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vma: Add VM_WARN_ON for commit_merge
Date: Thu, 16 Jan 2025 14:06:17 +0800	[thread overview]
Message-ID: <107e1d14-1a2c-48ff-8947-22e5d791f632@kylinos.cn> (raw)
In-Reply-To: <20250115200138.708adc518dd4f92f4fe7fae5@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 2697 bytes --]


在 2025/1/16 12:01, Andrew Morton 写道:
> On Thu, 16 Jan 2025 10:50:05 +0800 Liu Ye<liuye@kylinos.cn>  wrote:
>
>>      Add VM_WARN_ON to prevent 'adjust' from accessing NULL pointers
>>      when 'adjust' is NULL and 'expanded' is false or 'adj_start' is
>>      not zero.
>>
>> ...
>>
>> --- a/mm/vma.c
>> +++ b/mm/vma.c
>> @@ -641,6 +641,7 @@ static int commit_merge(struct vma_merge_struct *vmg,
>>   
>>   	init_multi_vma_prep(&vp, vmg->vma, adjust, remove, remove2);
>>   
>> +	VM_WARN_ON(!adjust && (!expanded || adj_start));
>>   	VM_WARN_ON(vp.anon_vma && adjust && adjust->anon_vma &&
>>   		   vp.anon_vma != adjust->anon_vma);
>>   
> This won't prevent a null deref.  It will emit a warning which
> duplicates all the information which we're about to emit from the oops
> handler.
Yes, the accurate description should be that an oops warning message will be
generated when the corresponding input parameter is illegal.  This helps to
find the problem.
> Are there any reports of an oops from a NULL deref of `adjust'?

This issue is not from any report yet, but by cppcheck tool only.

mm/vma.c:652:29: warning: Possible null pointer dereference: adjust 
[nullPointer]
   vma_iter_config(vmg->vmi, adjust->vm_start + adj_start,
                                                             ^
mm/vma.c:1072:24: note: Calling function 'commit_merge', 2nd argument 
'NULL' value is 0
  if (commit_merge(vmg, NULL, remove_next ? next : NULL, NULL, 0, true))
                                                    ^
mm/vma.c:652:29: note: Null pointer dereference
   vma_iter_config(vmg->vmi, adjust->vm_start + adj_start,
                                                             ^
mm/vma.c:653:5: warning: Possible null pointer dereference: adjust 
[nullPointer]
     adjust->vm_end);
     ^
mm/vma.c:1072:24: note: Calling function 'commit_merge', 2nd argument 
'NULL' value is 0
  if (commit_merge(vmg, NULL, remove_next ? next : NULL, NULL, 0, true))
                                                   ^
mm/vma.c:653:5: note: Null pointer dereference
     adjust->vm_end);
     ^


Before calling commit_merge, the correct relationship between adjust,
adj_start, and expanded must be ensured, such as the functions
vma_merge_existing_range and vma_expand. Therefore, VM_WARN_ON is added
inside the function to detect incorrect relationships. Of course,
commit_merge is not used anywhere else at present, so adding VM_WARN_ON
is just a suggestion.

[-- Attachment #2: Type: text/html, Size: 4159 bytes --]

  reply	other threads:[~2025-01-16  6:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  2:50 Liu Ye
2025-01-16  4:01 ` Andrew Morton
2025-01-16  6:06   ` liuye [this message]
2025-01-16  7:44 ` Lorenzo Stoakes

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=107e1d14-1a2c-48ff-8947-22e5d791f632@kylinos.cn \
    --to=liuye@kylinos.cn \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=vbabka@suse.cz \
    /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