Hello, On Thu, Jun 11, 2026 at 07:32:55PM +0200, Thomas Hellström wrote: > When writing a "max" limit lower than the current usage, the > existing code silently failed. This series aims to improve > on that by returning -EBUSY on failure and also attempt > to synchronously reclaim device memory to push the usage > under the new max limit to avoid the error.
The canonical behavior for cgroup2 would be not failing the write at all even when the usage can't be brought down below the new max. Updating the target configuration and tracking the current usage are separate operations. The former should just set max and trigger reclaim and a writer should not assume that a successful write indicates that the usage is below the written max value. Thanks. -- tejun
