[merged mm-stable] docs-mm-clarify-that-user_reserve_kbytes-has-no-effect-when-overcommit_memory-is-set-to-0-or-1.patch removed from -mm tree

[merged mm-stable] docs-mm-clarify-that-user_reserve_kbytes-has-no-effect-when-overcommit_memory-is-set-to-0-or-1.patch removed from -mm tree

[Andrew Morton]

The quilt patch titled
     Subject: docs: mm: clarify that user_reserve_kbytes has no effect when overcommit_memory is set to 0 or 1
has been removed from the -mm tree.  Its filename was
     docs-mm-clarify-that-user_reserve_kbytes-has-no-effect-when-overcommit_memory-is-set-to-0-or-1.patch

This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Brian Masney <bmasney@redhat.com>
Subject: docs: mm: clarify that user_reserve_kbytes has no effect when overcommit_memory is set to 0 or 1
Date: Thu, 28 May 2026 09:45:10 -0400

Looking at __vm_enough_memory() in mm/util.c, user_reserve_kbytes has no
effect when overcommit_memory is set to 0 or 1. The documentation for
overcommit_memory already references user_reserve_kbytes when the flag
is set to 2.

Let's go ahead and add a clarification to user_reserve_kbytes in vm.rst
that it has no effect when overcommit_memory is set to 0 or 1.

Link: https://lore.kernel.org/20260528-mm-clarify-docs-v1-1-aa88e83b4bfd@redhat.com
Signed-off-by: Brian Masney <bmasney@redhat.com>
Cc: David Hildenbrand <david@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/admin-guide/sysctl/vm.rst |    2 ++
 1 file changed, 2 insertions(+)

--- a/Documentation/admin-guide/sysctl/vm.rst~docs-mm-clarify-that-user_reserve_kbytes-has-no-effect-when-overcommit_memory-is-set-to-0-or-1
+++ a/Documentation/admin-guide/sysctl/vm.rst
@@ -1034,6 +1034,8 @@ min(3% of current process size, user_res
 This is intended to prevent a user from starting a single memory hogging
 process, such that they cannot recover (kill the hog).
 
+This setting has no effect when overcommit_memory is set to 0 or 1.
+
 user_reserve_kbytes defaults to min(3% of the current process size, 128MB).
 
 If this is reduced to zero, then the user will be allowed to allocate
_

Patches currently in -mm which might be from bmasney@redhat.com are