From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794046227; b=voixw0teT7X//nEslLTffOPKCpRSgTU7OYp26ZLispv4aN6dit003HoX7zvwI8qmy0d6 GVjFeRA58L+o/BqZQJGFZap6wbQKr4Y78MT5WC2R3UxU6WrFsBDjSvbCsa2+h3wbtDt9J KdYrDUrtAvPUY2ZVtU9E/WhDpYkMV0RCYHxkVU/EfU09f5jfvQck3wVi5lqx7+QhwiJKz OhkLFgODlCDw2FOSc2XF6dHztO9qQZZS+GscQwrcmwzdzWuoc77Wux9aaquR+mb/z7smB hyxPFCgsLgxKDPzuixU+DpksBUsA4ri0zihnZ7UULykMEDErm9IE7EtieaynzqDFfSQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794046227; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=dkn3p/uaYva8IuKj2LOY5SVfvzxQ28Qp3dwb6IgQbv0=; b=ObCR9kNpmb1r5/f20lDTlVkAO4tEkpGiSujPVsFP6/B17RihEYfu2G6zCtsA+WxDXc2O YT9qY1KSzRAEU06OgiJeSU168U8XrMoEhIhavSyzm5UlHoEyimwZRkVnXnUqiA9jIeFNu 0p+tOIH1NK2weQiMEdcqHyIdpQOFzbgTS26GM7orvq7ag14BZ2rRHo+470HWBgF6//JnC /PbDzeQbiPpjeBLKFIDGVg7v/Rf33nvjHg32kvm/KxJaBd2kdVuDuYTdXLt1+8ClMW21k RUikFn7WlY73fJ4og8cAhX71zn0U99R3spiETYqpdSjKYYZTakvoQs6ckKZIxmj7uPQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=YN+PXgd8; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D5FCE606A33B for ; Sat, 7 Nov 2026 10:10:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=YN+PXgd8 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1085D1F0089F; Sat, 7 Nov 2026 10:10:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794046226; bh=dkn3p/uaYva8IuKj2LOY5SVfvzxQ28Qp3dwb6IgQbv0=; h=From:To:Cc:Subject:Date; b=YN+PXgd8FzXatwfj/yCi9GABU+OWZBUGTwqpDxOIC0FscCJHm8fLRgyxp6aiqjHC7 0YEzVZeVJZ1CQMdNR4Ym17wLIccwsvZUkwp2U8d7tckohvhxLYteSIPD28c4DwNJNE vZ57Q2PuRrZMTz/1XP35eW74Rf6zeNqLLN7mOPA4BcnJUWUWFFcmt5IApmtYRxmzm+ nMMRHXyp3yu2JLESEhSvaoKlcirXetTgASL9qd9V7lIxYf9XotsLSCLsHEe/6TDJdC Ig+k0C5gNVlbV86Rmb2ptP0KGK7TsOiOyFrtTG/8Iaq03EjqQ160ZPJIQGmO7rLs4P hRqfAwgsOZYVA== From: Sasha Levin To: sj@kernel.org, akpm@linux-foundation.org, brendan.higgins@linux.dev, davidgow@davidgow.net, usamaarif642@gmail.com Cc: stable@vger.kernel.org Subject: FAILED: patch "[PATCH] mm/damon/core: disallow max < min damos filter range arguments commit" failed to apply to 6.18-stable tree Date: Sat, 7 Nov 2026 05:10:25 -0500 Message-ID: <20261107051024-failed-6.18-1bfb9384ae0e@kernel.org> X-Mailer: git-send-email 2.53.0 X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The patch below does not apply to the 6.18-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.18.y git checkout FETCH_HEAD git cherry-pick -x 1bfb9384ae0ed52d61eb601b655014b7815ff849 # git commit -s git send-email --to '' --in-reply-to '20261107051024-failed-6.18-1bfb9384ae0e@kernel.org' --subject-prefix 'PATCH 6.18.y' 'HEAD^..' Thanks, Sasha ------------------ original commit in Linus's tree ------------------ >From 1bfb9384ae0ed52d61eb601b655014b7815ff849 Mon Sep 17 00:00:00 2001 From: SJ Park Date: Mon, 14 Sep 2026 07:23:21 -0700 Subject: [PATCH] mm/damon/core: disallow max < min damos filter range arguments commit damos_commit_filter_arg() receives range arguments for a few types of DAMOS filters. It allows any range including max < min range. It is fine for the logic, but makes no sense to support it. Actually DAMON sysfs interface is doing the validation on its own. To avoid duplicated validations in multiple DAMON API callers, it would be better to do the validation in the core layer. Add a validation of the given range. Link: https://lore.kernel.org/20260914142327.92510-5-sj@kernel.org Signed-off-by: SJ Park Signed-off-by: Andrew Morton Cc: Brendan Higgins Cc: David Gow Cc: Usama Arif Cc: --- mm/damon/core.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/mm/damon/core.c b/mm/damon/core.c index 1932a50252079..5fdacb9dcee5f 100644 --- a/mm/damon/core.c +++ b/mm/damon/core.c @@ -1325,15 +1325,21 @@ static int damos_commit_filter_arg( dst->memcg_id = src->memcg_id; break; case DAMOS_FILTER_TYPE_ADDR: + if (src->addr_range.end < src->addr_range.start) + return -EINVAL; dst->addr_range = src->addr_range; break; case DAMOS_FILTER_TYPE_TARGET: dst->target_idx = src->target_idx; break; case DAMOS_FILTER_TYPE_HUGEPAGE_SIZE: + if (src->sz_range.max < src->sz_range.min) + return -EINVAL; dst->sz_range = src->sz_range; break; case DAMOS_FILTER_TYPE_PROBE_HITS_WSUM: + if (src->range_max < src->range_min) + return -EINVAL; dst->range_min = src->range_min; dst->range_max = src->range_max; break; -- 2.53.0