From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9B3093B6BF5; Mon, 4 May 2026 12:52:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777899148; cv=none; b=uIp0begIhiIarEmfSe5R5le/Nzr/UeKvcXm6Yd0LX6sacHQ8hJ8Op6nC/EPepfzmxcEP6skw14by11brNydEtGlo3L1XlJ2UhwjC/vEA6XK0EpLRnWNP1g1nn6Kyet+otcFqDnjc2eo7YFmkRLYP5ACjm23uw4C9xI3QCOyNMPE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777899148; c=relaxed/simple; bh=4UagUZ8wRB0GvAntGaBzkSiwV6j2AGcjkb7wsKZZLwQ=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=a5/Kst4Nq2fqTln+gmEt7f23Rp+sZPJgVel598Ot9+tlpxsEw9PhlX1Noyndf7UVgR66OwmM1LCWWph+I4vRD1xnRb9aJcft5PzBi8e3ibpwD7XvW9RpOyGbcQwvcjtl/1GZfy6EktmHKy76R/FnsAcgh5bhi3O1ApoCsrnaLFo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=oYq6dJlJ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="oYq6dJlJ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 54D0BC2BCB8; Mon, 4 May 2026 12:52:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1777899148; bh=4UagUZ8wRB0GvAntGaBzkSiwV6j2AGcjkb7wsKZZLwQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=oYq6dJlJuQFEiy+Zc4UhQOB1sYDkGSPps0iHDmUe9Y3xt+GXOtkXCtqqwdOkog3AW 5urSVqWe7/zacO+IfqXHj2OT2qB199QLhnxcXwwxC0bd6k5gjvf2gPuMKwZn2fob15 bJ1DRuZoYsnt+Ldn4OhlnvUYVBvQex0KQ4tLp/oqIb+ZtxfllX4g/jvRGaN7gdHJv+ Z8Od2a28BzwXyJ7qYVZNrKBMk+kd8WJUlxi6eREfiXgMz3hsELXF7a2tiMLfQJtDqq 90J04Yr+HNw04kToN2Zrd/gG+2TVsEwFdfqFvoOVi12l4kGeYd8q7GFfBp01QQOoRT BpBSoqXVMUqwQ== From: SeongJae Park To: stable@vger.kernel.org Cc: damon@lists.linux.dev, SeongJae Park , Andrew Morton Subject: [PATCH 6.12.y] mm/damon/core: disallow time-quota setting zero esz Date: Mon, 4 May 2026 05:52:20 -0700 Message-ID: <20260504125220.15509-1-sj@kernel.org> X-Mailer: git-send-email 2.47.3 In-Reply-To: <2026050313-giddy-quizzical-4cc1@gregkh> References: <2026050313-giddy-quizzical-4cc1@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit When the throughput of a DAMOS scheme is very slow, DAMOS time quota can make the effective size quota smaller than damon_ctx->min_region_sz. In the case, damos_apply_scheme() will skip applying the action, because the action is tried at region level, which requires >=min_region_sz size. That is, the quota is effectively exceeded for the quota charge window. Because no action will be applied, the total_charged_sz and total_charged_ns are also not updated. damos_set_effective_quota() will try to update the effective size quota before starting the next charge window. However, because the total_charged_sz and total_charged_ns have not updated, the throughput and effective size quota are also not changed. Since effective size quota can only be decreased, other effective size quota update factors including DAMOS quota goals and size quota cannot make any change, either. As a result, the scheme is unexpectedly deactivated until the user notices and mitigates the situation. The users can mitigate this situation by changing the time quota online or re-install the scheme. While the mitigation is somewhat straightforward, finding the situation would be challenging, because DAMON is not providing good observabilities for that. Even if such observability is provided, doing the additional monitoring and the mitigation is somewhat cumbersome and not aligned to the intention of the time quota. The time quota was intended to help reduce the user's administration overhead. Fix the problem by setting time quota-modified effective size quota be at least min_region_sz always. The issue was discovered [1] by sashiko. Link: https://lore.kernel.org/20260407003153.79589-1-sj@kernel.org Link: https://lore.kernel.org/20260405192504.110014-1-sj@kernel.org [1] Fixes: 1cd243030059 ("mm/damon/schemes: implement time quota") Signed-off-by: SeongJae Park Cc: # 5.16.x Signed-off-by: Andrew Morton (cherry picked from commit 8bbde987c2b84f80da0853f739f0a920386f8b99) Signed-off-by: SeongJae Park --- mm/damon/core.c | 1 + 1 file changed, 1 insertion(+) diff --git a/mm/damon/core.c b/mm/damon/core.c index ed2b75023181..69f8244324b3 100644 --- a/mm/damon/core.c +++ b/mm/damon/core.c @@ -1577,6 +1577,7 @@ static void damos_set_effective_quota(struct damos_quota *quota) esz = min(throughput * quota->ms, esz); else esz = throughput * quota->ms; + esz = max(DAMON_MIN_REGION, esz); } if (quota->sz && quota->sz < esz) -- 2.47.3