From: Uladzislau Rezki <urezki@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Uladzislau Rezki <urezki@gmail.com>, Dev Jain <dev.jain@arm.com>,
Ye Liu <ye.liu@linux.dev>, Ye Liu <liuye@kylinos.cn>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: vmalloc: fix vmap_purge_lock livelock under memory pressure
Date: Tue, 1 Sep 2026 18:36:42 +0200 [thread overview]
Message-ID: <apb_Grl4I5o2dxKY@milan> (raw)
In-Reply-To: <20260831184252.15b978678820a94b106640ac@linux-foundation.org>
On Mon, Aug 31, 2026 at 06:42:52PM -0700, Andrew Morton wrote:
> On Mon, 31 Aug 2026 11:54:22 +0200 Uladzislau Rezki <urezki@gmail.com> wrote:
>
> > But, i think we can overt mutex_lock() into mutex_trylock() just only
> > in the:
> >
> > static unsigned long
> > vmap_node_shrink_scan(struct shrinker *shrink, struct shrink_control *sc)
> > {
> > struct vmap_node *vn;
> >
> > guard(mutex)(&vmap_purge_lock);
> > for_each_vmap_node(vn)
> > decay_va_pool_node(vn, true);
> >
> > return SHRINK_STOP;
> > }
>
> I *think* that means we can expect a v3.
>
> Ho hum. I guess I'll queue v2, under the assumption that my
> assumptions are usually wrong.
>
Yep :)
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-09-01 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 9:17 [PATCH v2] mm: vmalloc: fix vmap_purge_lock livelock under memory pressure Ye Liu
2026-08-28 16:54 ` Uladzislau Rezki
2026-08-28 18:05 ` Andrew Morton
2026-08-31 6:09 ` Dev Jain
2026-08-31 9:54 ` Uladzislau Rezki
2026-09-01 1:42 ` Andrew Morton
2026-09-01 16:36 ` Uladzislau Rezki [this message]
2026-09-01 6:22 ` Dev Jain
2026-09-01 9:07 ` Ye Liu
2026-09-01 16:43 ` Uladzislau Rezki
2026-09-01 16:59 ` Uladzislau Rezki
2026-09-02 4:30 ` Dev Jain
2026-09-03 9:10 ` Uladzislau Rezki
2026-09-01 16:40 ` 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=apb_Grl4I5o2dxKY@milan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=ye.liu@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.