XPost: linux.debian.kernel

I booted the new kernel this morning. Using cgroupv2 I got

% docker run -it --rm -m 4g --cpus=3 debian:trixie
root@b46ebbb70b04:/# apt update
Get:1 http://deb.debian.org/debian trixie InRelease [168 kB]
Get:2 http://deb.debian.org/debian trixie-updates InRelease [45.1 kB]
Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB] Get:4 http://deb.debian.org/debian trixie/main amd64 Packages [9672 kB]
Get:5 http://deb.debian.org/debian-security trixie-security/main amd64 Packages [5304 B]
Fetched 9934 kB in 1s (9313 kB/s)
13 packages can be upgraded. Run 'apt list --upgradable' to see them. root@b46ebbb70b04:/# apt -y install default-jdk
:
:
root@b46ebbb70b04:/# java -Xlog:os+container=trace --version [0.001s][trace][os,container] OSContainer::init: Initializing Container Support [0.001s][debug][os,container] Detected optional cpuset controller entry in /proc/cgroups
[0.001s][debug][os,container] Detected optional pids controller entry in /proc/cgroups
[0.002s][debug][os,container] Detected cgroups v2 unified hierarchy [0.002s][trace][os,container] Path to /cpu.max is /sys/fs/cgroup/cpu.max [0.002s][trace][os,container] Raw value for CPU quota is: 300000 [0.002s][trace][os,container] CPU Quota is: 300000 [0.002s][trace][os,container] Path to /cpu.max is /sys/fs/cgroup/cpu.max [0.002s][trace][os,container] CPU Period is: 100000 [0.002s][trace][os,container] CPU Quota count based on quota/period: 3 [0.002s][trace][os,container] OSContainer::active_processor_count: 3 [0.002s][trace][os,container] CgroupSubsystem::active_processor_count (cached): 3
[0.002s][trace][os,container] total physical memory: 67099267072 [0.002s][trace][os,container] Path to /memory.max is /sys/fs/cgroup/memory.max [0.002s][trace][os,container] Raw value for memory limit is: 4294967296 [0.002s][trace][os,container] Memory Limit is: 4294967296 [0.004s][trace][os,container] CgroupSubsystem::active_processor_count (cached): 3
[0.027s][trace][os,container] Path to /cpu.max is /sys/fs/cgroup/cpu.max [0.027s][trace][os,container] Raw value for CPU quota is: 300000 [0.027s][trace][os,container] CPU Quota is: 300000 [0.027s][trace][os,container] Path to /cpu.max is /sys/fs/cgroup/cpu.max [0.027s][trace][os,container] CPU Period is: 100000 [0.027s][trace][os,container] CPU Quota count based on quota/period: 3 [0.027s][trace][os,container] OSContainer::active_processor_count: 3
openjdk 21.0.7 2025-04-15
OpenJDK Runtime Environment (build 21.0.7+6-Debian-1)
OpenJDK 64-Bit Server VM (build 21.0.7+6-Debian-1, mixed mode, sharing)


This looks as expected. CPU and memory limits are correct. Now I have
to wait for a backport for Bookworm to roll out the new kernel to our developers and to our Kubernetes nodes.


Thank you very much. I highly appreciate your contribution to
Debian.


Harri

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.kernel

Applied to cgroup/for-6.17.

I would recommend to follow upstream for kernels beyond
Trixie in this aspect. Debian needs a workaround for kernel
6.12 in Trixie, because there are no JDKs fully compatible
with cgroupv2 yet, including the brand-new

OpenJDK 11.0.28
OpenJDK 17.0.16
OpenJDK 21.0.8

released a few days ago. I expect the JDKs will be fixed for
Forky.

Just my $0.02 of course. Regards
Harri

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.kernel

Hi,

On Mon, Jul 21, 2025 at 09:42:23AM +0200, Harald Dunkel wrote:

Applied to cgroup/for-6.17.

I would recommend to follow upstream for kernels beyond
Trixie in this aspect. Debian needs a workaround for kernel
6.12 in Trixie, because there are no JDKs fully compatible
with cgroupv2 yet, including the brand-new

OpenJDK 11.0.28
OpenJDK 17.0.16
OpenJDK 21.0.8

released a few days ago. I expect the JDKs will be fixed for
Forky.

This would be my "personal" (in terms of keeping deltas in the
packaging) preference:
- make sure the patches get backported down to 6.12.y
- drop our local revert
- make uses affected made aware of the kernel parameter to use (maybe
via a NEWS entry?)

I had a short discussion on IRC with Ben about that, and as the
upstream changes are not yet down to 6.12.y the situation is rather
clear that we have the revert. If the changes goes down to 6.12.y
though I would love to rediscuss if we could consider the above
instread.

I though realize it is too early to at all consider, given it's not
yet applied upsream.

Regards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)