From: Andrew Morton <akpm@linux-foundation.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Vasily Averin <vvs@virtuozzo.com>,
cgel.zte@gmail.com, shakeelb@google.com, rdunlap@infradead.org,
dbueso@suse.de, unixbhaskar@gmail.com, chi.minghao@zte.com.cn,
arnd@arndb.de, Zeal Robot <zealci@zte.com.cn>,
linux-mm@kvack.org, 1vier1@web.de, stable@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH] mm/util.c: Make kvfree() safe for calling while holding spinlocks
Date: Wed, 26 Jan 2022 18:53:40 -0800 [thread overview]
Message-ID: <20220126185340.58f88e8e1b153b6650c83270@linux-foundation.org> (raw)
In-Reply-To: <20211222194828.15320-1-manfred@colorfullife.com>
On Wed, 22 Dec 2021 20:48:28 +0100 Manfred Spraul <manfred@colorfullife.com> wrote:
> One codepath in find_alloc_undo() calls kvfree() while holding a spinlock.
> Since vfree() can sleep this is a bug.
>
> Previously, the code path used kfree(), and kfree() is safe to be called
> while holding a spinlock.
>
> Minghao proposed to fix this by updating find_alloc_undo().
>
> Alternate proposal to fix this: Instead of changing find_alloc_undo(),
> change kvfree() so that the same rules as for kfree() apply:
> Having different rules for kfree() and kvfree() just asks for bugs.
>
> Disadvantage: Releasing vmalloc'ed memory will be delayed a bit.
I know we've been around this loop a bunch of times and deferring was
considered. But I forget the conclusion. IIRC, mhocko was involved?
> --- a/mm/util.c
> +++ b/mm/util.c
> @@ -610,12 +610,12 @@ EXPORT_SYMBOL(kvmalloc_node);
> * It is slightly more efficient to use kfree() or vfree() if you are certain
> * that you know which one to use.
> *
> - * Context: Either preemptible task context or not-NMI interrupt.
> + * Context: Any context except NMI interrupt.
> */
> void kvfree(const void *addr)
> {
> if (is_vmalloc_addr(addr))
> - vfree(addr);
> + vfree_atomic(addr);
> else
> kfree(addr);
> }
next prev parent reply other threads:[~2022-01-27 2:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 19:48 [PATCH] mm/util.c: Make kvfree() safe for calling while holding spinlocks Manfred Spraul
2021-12-23 3:40 ` Davidlohr Bueso
2021-12-23 7:21 ` Vasily Averin
2021-12-23 11:52 ` Manfred Spraul
2021-12-23 12:34 ` Vasily Averin
2021-12-25 18:54 ` Uladzislau Rezki
2021-12-25 22:58 ` Matthew Wilcox
2021-12-26 17:57 ` Uladzislau Rezki
2021-12-28 19:45 ` Uladzislau Rezki
2021-12-28 20:04 ` Manfred Spraul
2021-12-28 20:26 ` Uladzislau Rezki
2022-01-27 2:53 ` Andrew Morton [this message]
2022-01-27 5:59 ` Manfred Spraul
2022-01-27 8:25 ` Michal Hocko
2022-01-27 15:54 ` Uladzislau Rezki
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=20220126185340.58f88e8e1b153b6650c83270@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=1vier1@web.de \
--cc=arnd@arndb.de \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=mhocko@kernel.org \
--cc=rdunlap@infradead.org \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=unixbhaskar@gmail.com \
--cc=vvs@virtuozzo.com \
--cc=zealci@zte.com.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;
as well as URLs for NNTP newsgroup(s).