linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Екатерина Есина" <eesina@astralinux.ru>
To: David Hildenbrand <david@redhat.com>,
	Mike Kravetz <mike.kravetz@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org
Subject: Re: [PATCH mm] mm: hugetlb: Add checks for NULL for vma returned from find_vma. find_vma may return NULL, that's why its return value is usually checked for NULL.
Date: Mon, 16 Jan 2023 18:10:18 +0300 (MSK)	[thread overview]
Message-ID: <182575210.374192581.1673881818398.JavaMail.zimbra@astralinux.ru> (raw)
In-Reply-To: <6f5ac7ee-0af3-a466-cf7f-b17270bc1391@redhat.com>

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


 Sorry, I've noticed that I'd sent the patch without description and sent version 2.   Function find_vma may return NULL, that's why its return value is usually checked for NULL. In this case vma and its fields also should be checked before dereferencing to avoid NULL pointer dereference   Best regards, Ekaterina Esina  
   
   

-----Original Message-----

From: David <david@redhat.com>
To: Esina <eesina@astralinux.ru>; Mike <mike.kravetz@oracle.com>
Cc: Andrew <akpm@linux-foundation.org>; linux-mm <linux-mm@kvack.org>; linux-kernel <linux-kernel@vger.kernel.org>; lvc-project <lvc-project@linuxtesting.org>
Date: Monday, 16 January 2023 4:24 PM MSK
Subject: Re: [PATCH mm] mm: hugetlb: Add checks for NULL for vma returned from find_vma. find_vma may return NULL, that's why its return value is usually checked for NULL.

On 16.01.23 11:05, Esina Ekaterina wrote: 
> Found by Astra Linux on behalf of Linux Verification Center 
> (linuxtesting.org) with SVACE. 

Please trim the subject and move details to the description. 

What are the symptoms? How exactly does this BUG manifest? What is this 
patch fixing? 


-- 
Thanks, 

David / dhildenb 

  

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

  parent reply	other threads:[~2023-01-16 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230116100520.71277-1-eesina@astralinux.ru>
2023-01-16 13:24 ` David Hildenbrand
2023-01-16 15:05   ` Екатерина Есина
2023-01-16 15:10   ` Екатерина Есина [this message]
2023-01-16 15:12     ` David Hildenbrand
2023-01-16 15:21       ` Matthew Wilcox

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=182575210.374192581.1673881818398.JavaMail.zimbra@astralinux.ru \
    --to=eesina@astralinux.ru \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=mike.kravetz@oracle.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