From: Vasily Averin <vvs@virtuozzo.com>
To: Manfred Spraul <manfred@colorfullife.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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
Subject: Re: [PATCH] mm/util.c: Make kvfree() safe for calling while holding spinlocks
Date: Thu, 23 Dec 2021 15:34:26 +0300 [thread overview]
Message-ID: <f24d2e3f-1dfd-7bf4-78fa-4eb515b4cd7c@virtuozzo.com> (raw)
In-Reply-To: <937f1320-6b7e-9aa2-2a21-7fd2f94eeb32@colorfullife.com>
On 23.12.2021 14:52, Manfred Spraul wrote:
> Hello Vasily,
>
> On 12/23/21 08:21, Vasily Averin wrote:
>>
>> I would prefer to release memory ASAP if it's possible.
>> What do you think about this change?
>> --- a/mm/util.c
>> +++ b/mm/util.c
>> @@ -614,9 +614,12 @@ EXPORT_SYMBOL(kvmalloc_node);
>> */
>> void kvfree(const void *addr)
>> {
>> - if (is_vmalloc_addr(addr))
>> - vfree(addr);
>> - else
>> + if (is_vmalloc_addr(addr)) {
>> + if (in_atomic())
>> + vfree_atomic();
>> + else
>> + vfree(addr);
>> + } else
>> kfree(addr);
>> }
>> EXPORT_SYMBOL(kvfree);
>>
> Unfortunately this cannot work:
yes, you're right and I do not see any better solution yet.
next prev parent reply other threads:[~2021-12-23 12:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 19:48 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 [this message]
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
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=f24d2e3f-1dfd-7bf4-78fa-4eb515b4cd7c@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=1vier1@web.de \
--cc=akpm@linux-foundation.org \
--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=rdunlap@infradead.org \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=unixbhaskar@gmail.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