config: add new options for 6.12 kernel

Since kernel v6.12 couple more options were added to
CGROUP section. Add them here to avoid missing symbols.

Signed-off-by: Mantas Pucka <mantas@8devices.com>
Link: https://github.com/openwrt/openwrt/pull/16547
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>

diff --git a/config/Config-kernel.in b/config/Config-kernel.in
index 31d0e2dba4ec2a69a2bfc0186c28aeb2913d2f01..95bcc2146a6fd1922c8f14602b0d89b48b571348 100644 (file)
--- a/config/Config-kernel.in
+++ b/config/Config-kernel.in
@@ -861,6 +861,18 @@ if KERNEL_CGROUPS
                  Memory Nodes and assigning tasks to run only within those sets.
                  This is primarily useful on large SMP or NUMA systems.
 
+       config KERNEL_CPUSETS_V1
+               bool "Legacy cgroup v1 cpusets controller"
+               depends on KERNEL_CPUSETS
+               depends on !LINUX_6_6
+               default n
+               help
+                 Legacy cgroup v1 cpusets controller which has been deprecated by
+                 cgroup v2 implementation. The v1 is there for legacy applications
+                 which haven't migrated to the new cgroup v2 interface yet. If you
+                 do not have any such application then you are completely fine leaving
+                 this option disabled.
+
        config KERNEL_PROC_PID_CPUSET
                bool "Include legacy /proc/<pid>/cpuset file"
                depends on KERNEL_CPUSETS
@@ -952,6 +964,22 @@ if KERNEL_CGROUPS
                  Memory Controller, which are page-based, and can be swapped. Users of
                  the kmem extension can use it to guarantee that no group of processes
                  will ever exhaust kernel resources alone.
+       
+       config KERNEL_MEMCG_V1
+               bool "Legacy cgroup v1 memory controller"
+               default n
+               depends on KERNEL_MEMCG
+               depends on !LINUX_6_6
+               help
+                 Legacy cgroup v1 memory controller which has been deprecated by
+                 cgroup v2 implementation. The v1 is there for legacy applications
+                 which haven't migrated to the new cgroup v2 interface yet. If you
+                 do not have any such application then you are completely fine leaving
+                 this option disabled.
+
+                 Please note that feature set of the legacy memory controller is likely
+                 going to shrink due to deprecation process. New deployments with v1
+                 controller are highly discouraged.
 
        config KERNEL_CGROUP_PERF
                bool "Enable perf_event per-cpu per-container group (cgroup) monitoring"