From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Gregory Price (Meta)" <gourry@gourry.net>
Cc: Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Zi Yan <ziy@nvidia.com>, Joshua Hahn <joshua.hahnjy@gmail.com>,
Rakie Kim <rakie.kim@sk.com>,
Ying Huang <ying.huang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] mm/mempolicy: limit shared policy ranges per inode
Date: Sun, 15 Nov 2026 17:40:31 +0100 [thread overview]
Message-ID: <76fc4555-b458-491b-ba2c-ec030879dafe@kernel.org> (raw)
In-Reply-To: <179468794889.482102.14066028910704780583.b4-reply@b4>
On 11/14/26 21:25, Gregory Price (Meta) wrote:
> On 2026-11-14 21:16 +0100, David Hildenbrand (Arm) wrote:
>> On 11/14/26 18:41, Gregory Price (Meta) wrote:
>>>
>>> Multi-task mappers were previously unlimited, but that seems like more
>>> of a nasty unintended corner case - not a real feature.
>>>
>>> A single process is already limited on the number of vmas/policies based
>>> on `max_map_count`, so it seems natural to just use max_map_count
>>> directly, but I took a brief look at some distros and most seem to
>>> ship a raised `max_map_count` (>1 million) by default).
>>>
>>> I tested that and even 1 million can cause a soft lockup.
>>>
>>> Not sure there's an easy solution here, we might have to rework the shm
>>> policy locks.
>>
>> Do you know a single valid use case that's not solved by patch #1 and would
>> trigger that many policies?
>>
>> Ai was not able to come up with anything for me.
>
> Just want to make sure the bases are covered.
>
Yes, and I'd be very happy to learn about use cases.
Maybe we can let this stay in -next for a while before moving forward with this?
> If others are ok with this change, it doesn't look unreasonable to me.
>
> Although I'd wonder whether just using max_map_count's limit instead of
> adding a new toggle would just be cleaner and avoid adding a new uapi.
I considered it but discarded that. Having 1mil on Fedora et al is not
particularly helpful. Both are related but, in practice, completely separate
concepts.
--
Cheers,
David
next prev parent reply other threads:[~2026-11-15 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 21:36 [PATCH 0/2] mm/mempolicy: shared policy limits for tmpfs/shmem/guest_memfd David Hildenbrand (Arm)
2026-11-13 21:36 ` [PATCH 1/2] mm/mempolicy: merge adjacent shared policy ranges David Hildenbrand (Arm)
2026-11-13 22:23 ` Joshua Hahn
2026-11-14 17:22 ` Gregory Price (Meta)
2026-11-16 16:49 ` Zi Yan
2026-11-13 21:36 ` [PATCH 2/2] mm/mempolicy: limit shared policy ranges per inode David Hildenbrand (Arm)
2026-11-14 17:41 ` Gregory Price (Meta)
2026-11-14 20:16 ` David Hildenbrand (Arm)
2026-11-14 20:25 ` Gregory Price (Meta)
2026-11-15 16:40 ` David Hildenbrand (Arm) [this message]
2026-11-16 16:13 ` Gregory Price (Meta)
2026-11-16 22:17 ` David Hildenbrand (Arm)
2026-11-17 21:35 ` [PATCH 0/2] mm/mempolicy: shared policy limits for tmpfs/shmem/guest_memfd David Hildenbrand
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=76fc4555-b458-491b-ba2c-ec030879dafe@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=gourry@gourry.net \
--cc=hughd@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rakie.kim@sk.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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 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.