From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Balbir Singh <balbirs@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Gregory Price <gourry@gourry.net>, Zi Yan <ziy@nvidia.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Rakie Kim <rakie.kim@sk.com>,
Ying Huang <ying.huang@linux.alibaba.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Michal Hocko <mhocko@suse.com>, Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Lukas Czerner <lczerner@redhat.com>,
Carlos Maiolino <cmaiolino@redhat.com>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Daniel Verkamp <dverkamp@chromium.org>,
Jeff Xu <jeffxu@google.com>, Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
David Stevens <stevensd@chromium.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
William Kucharski <william.kucharski@oracle.com>,
Chris Li <chrisl@kernel.org>, Kairui Song <kasong@tencent.com>,
Nhat Pham <nphamcs@gmail.com>, Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Chris Mason <mason@kernel.org>,
stable@vger.kernel.org, Pedro Falcato <pfalcato@suse.de>,
"Kiryl Shutsemau (Meta)" <kas@kernel.org>
Subject: Re: [PATCH v3 01/15] mm/mempolicy: charge shared policy nodes
Date: Wed, 28 Oct 2026 11:06:46 +0100 [thread overview]
Message-ID: <11c6fd13-d2a2-4497-8417-d2176f1b5ecf@kernel.org> (raw)
In-Reply-To: <auHINbCObZYzpNqC@parvat>
On 10/28/26 11:02, Balbir Singh wrote:
> On Wed, Oct 28, 2026 at 10:54:59AM +0100, David Hildenbrand (Arm) wrote:
>> From: Chris Mason <mason@kernel.org>
>>
>> Any local user can bypass memory.max with mbind() on a tmpfs file, and
>> allocate unbounded kernel memory.
>>
>> mbind() sets a NUMA memory policy for a range of a mapping. If the
>> mapping is of a shmem and friends, the kernel also stores the policy on
>> the inode, in a tree with one entry per range of the file.
>>
>> Each mbind() on a single page of a mapping can add one shared policy node
>> (struct sp_node) and one struct mempolicy to that tree. They outlive the
>> mapping and stay around until the inode is destroyed. The tree is not
>> bounded by the file size, so the file can be empty.
>>
>> Memory that user space can allocate must be charged to a memory cgroup. A
>> slab cache does that for all of its objects if it is created with
>> SLAB_ACCOUNT. numa_policy_init() creates the slab caches for both
>> structs without SLAB_ACCOUNT, so they are not charged to any cgroup.
>>
>> Reproduced with mbind() on single pages of an empty tmpfs file, from a
>> cgroup with memory.max=8M: the global OOM killer killed tasks owned by
>> root, and the machine panicked.
>>
>> Fix this by creating both caches with SLAB_ACCOUNT. This change implies
>> that mbind() can now fail when running into memcg limits. Further,
>> the policy_cache also serves task and VMA policies, so they are
>> similarly accounted now.
>>
>> Note that per-file limits are not really helpful, as the user could
>> simply use many files; having limits per user is tricky as well.
>>
>> Fix generated by an LLM and submitted by Chris Mason in private.
>>
>> Fixes: 5d097056c9a0 ("kmemcg: account certain kmem allocations to memcg")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Chris Mason <mason@kernel.org>
>> Acked-by: Pedro Falcato <pfalcato@suse.de>
>> Acked-by: Kiryl Shutsemau (Meta) <kas@kernel.org>
>> Acked-by: Zi Yan <ziy@nvidia.com>
>> Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> Tested-by: Gregory Price (Meta) <gourry@gourry.net>
>> [ david: smaller description tweaks ]
>> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>> ---
>> mm/mempolicy.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
>> index 0884c629670d..4da1cb8777f6 100644
>> --- a/mm/mempolicy.c
>> +++ b/mm/mempolicy.c
>> @@ -3372,11 +3372,11 @@ void __init numa_policy_init(void)
>>
>> policy_cache = kmem_cache_create("numa_policy",
>> sizeof(struct mempolicy),
>> - 0, SLAB_PANIC, NULL);
>> + 0, SLAB_PANIC | SLAB_ACCOUNT, NULL);
>>
>> sn_cache = kmem_cache_create("shared_policy_node",
>> sizeof(struct sp_node),
>> - 0, SLAB_PANIC, NULL);
>> + 0, SLAB_PANIC | SLAB_ACCOUNT, NULL);
>>
>> for_each_node(nid) {
>> preferred_node_policy[nid] = (struct mempolicy) {
>>
>
> You have many of them already, but anyway
>
> Reviewed-by: Balbir Singh <balbirs@nvidia.com>
I love it, thanks to all of you :)
--
Cheers,
David
next prev parent reply other threads:[~2026-10-28 10:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 9:54 [PATCH v3 00/15] mm/shmem: various (urgent?) fixes David Hildenbrand (Arm)
2026-10-28 9:54 ` [PATCH v3 01/15] mm/mempolicy: charge shared policy nodes David Hildenbrand (Arm)
2026-10-28 10:02 ` Balbir Singh
2026-10-28 10:06 ` David Hildenbrand (Arm) [this message]
2026-10-28 9:55 ` [PATCH v3 02/15] tmpfs: keep the quota soft limits of an unused id David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 03/15] tmpfs: preserve explicitly disabled quota limits David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 04/15] mm/shmem: honour F_SEAL_EXEC when an ACL is set David Hildenbrand (Arm)
2026-10-28 10:06 ` Balbir Singh
2026-10-28 9:55 ` [PATCH v3 05/15] hugetlbfs: enforce F_SEAL_EXEC in setattr David Hildenbrand (Arm)
2026-10-28 10:51 ` Oscar Salvador (SUSE)
2026-10-28 9:55 ` [PATCH v3 06/15] mm/shmem: hold off eviction in shmem_writeout() David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 07/15] mm/shmem: stop retrying folios that cannot be split David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 08/15] mm/shmem: preserve data in clean folios when splitting fails David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 09/15] mm/shmem: discard whole new large folios on fallocate rollback David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 10/15] mm/shmem: rescan after nonuniform folio splitting David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 11/15] mm/shmem: fix truncate hang in large swap entry David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 12/15] mm/shmem: preserve allocation errors when swapping in large entries David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 13/15] mm/shmem: fix truncate loop after boundary swapin failure David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 14/15] mm/shmem: fix accounting of swapin-error markers David Hildenbrand (Arm)
2026-10-28 9:55 ` [PATCH v3 15/15] mm/shmem: fix truncation of files containing only " David Hildenbrand (Arm)
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=11c6fd13-d2a2-4497-8417-d2176f1b5ecf@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=chrisl@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=dverkamp@chromium.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=jeffxu@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=lczerner@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mason@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=nphamcs@gmail.com \
--cc=osalvador@suse.de \
--cc=pfalcato@suse.de \
--cc=rakie.kim@sk.com \
--cc=stable@vger.kernel.org \
--cc=stevensd@chromium.org \
--cc=vdavydov.dev@gmail.com \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®