From: Christoph Hellwig <hch@infradead.org>
To: Alexander Sapozhnikov <alsp705@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] mm/vmalloc: fix unsafe dereference of potential null ptr in vmalloc_init()
Date: Fri, 17 Feb 2023 07:35:28 -0800 [thread overview]
Message-ID: <Y++ewLr68kfX6q9r@infradead.org> (raw)
In-Reply-To: <20230217125105.12385-1-alsp705@gmail.com>
On Fri, Feb 17, 2023 at 03:51:05PM +0300, Alexander Sapozhnikov wrote:
> Return value of a function 'kmem_cache_create' is dereferenced
> at vmalloc.c:2444 without checking for null, but it is usually
> checked for this function.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
I think that checker needs to learn about SLAB_PANIC..
prev parent reply other threads:[~2023-02-17 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 12:51 [PATCH] mm/vmalloc: fix unsafe dereference of potential null ptr in vmalloc_init() Alexander Sapozhnikov
2023-02-17 15:35 ` Christoph Hellwig [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=Y++ewLr68kfX6q9r@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alsp705@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lvc-project@linuxtesting.org \
--cc=urezki@gmail.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;
as well as URLs for NNTP newsgroup(s).