From: Matthew Wilcox <willy@infradead.org>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Paul Menzel <pmenzel+linux-kasan-dev@molgen.mpg.de>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH] mm/kasan: Don't vfree() nonexistent vm_area.
Date: Fri, 2 Feb 2018 09:20:27 -0800 [thread overview]
Message-ID: <20180202172027.GB16840@bombadil.infradead.org> (raw)
In-Reply-To: <e1cf8e8e-4cc4-ff4f-92e1-f6fcf373c67f@virtuozzo.com>
On Thu, Feb 01, 2018 at 11:22:55PM +0300, Andrey Ryabinin wrote:
> >> + vm = find_vm_area((void *)shadow_start);
> >> + if (vm)
> >> + vfree((void *)shadow_start);
> >> + }
> >
> > This looks like a complicated way to spell 'is_vmalloc_addr' ...
> >
>
> It's not. shadow_start is never vmalloc address.
I'm confused. How can you call vfree() on something that isn't a vmalloc
address?
next prev parent reply other threads:[~2018-02-02 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 16:46 Trying to vfree() nonexistent vm area (000000005d3b34b9) Paul Menzel
2018-02-01 16:33 ` [PATCH] mm/kasan: Don't vfree() nonexistent vm_area Andrey Ryabinin
2018-02-01 19:57 ` Matthew Wilcox
2018-02-01 20:22 ` Andrey Ryabinin
2018-02-02 17:20 ` Matthew Wilcox [this message]
2018-02-05 8:48 ` Andrey Ryabinin
2018-05-18 15:57 ` David Hildenbrand
2018-05-18 16:01 ` David Hildenbrand
2018-05-22 16:44 ` Andrey Ryabinin
2018-05-22 21:03 ` Andrew Morton
2018-05-23 12:33 ` Andrey Ryabinin
2018-05-26 3:31 ` [PATCH] mm-kasan-dont-vfree-nonexistent-vm_area-fix kbuild test robot
2018-05-26 3:48 ` Andrew Morton
2018-05-28 4:13 ` Ian Kent
2018-05-28 4:39 ` Ian Kent
2018-05-29 4:01 ` Ian Kent
2018-05-30 11:53 ` kbuild test robot
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=20180202172027.GB16840@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pmenzel+linux-kasan-dev@molgen.mpg.de \
--cc=stable@vger.kernel.org \
/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).