diff options
| author | SJ Park <sj@kernel.org> | 2026-09-14 07:23:21 -0700 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2026-09-29 23:13:23 -0700 |
| commit | 283d4e0502e2f568e6634f4b08e16ebaa3fa9ab1 (patch) | |
| tree | 502e95e299c35237803364f399e1e524949e53d1 /scripts/patch-kernel | |
| parent | d991a9f99c1e701bd600754035a1f5966cda5619 (diff) | |
| download | linux-next-283d4e0502e2f568e6634f4b08e16ebaa3fa9ab1.tar.gz linux-next-283d4e0502e2f568e6634f4b08e16ebaa3fa9ab1.zip | |
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 <sj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Brendan Higgins <brendan.higgins@linux.dev>
Cc: David Gow <davidgow@davidgow.net>
Cc: Usama Arif <usamaarif642@gmail.com>
Cc: <stable@vger.kernel.org>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions
