DAMON development mailing list
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.1 06/10] mm/damon/tests/core-kunit: test overlapping ranges for set_regions()
Date: Tue, 28 Jul 2026 20:56:11 -0700	[thread overview]
Message-ID: <20260729035613.131661-1-sj@kernel.org> (raw)
In-Reply-To: <20260729034822.AE14B1F000E9@smtp.kernel.org>

On Wed, 29 Jul 2026 03:48:22 +0000 sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Typo in comment: 'alingment' should be 'alignment'.
> --
> 
> --- Patch [6]: [RFC PATCH v1.1 06/10] mm/damon/tests/core-kunit: test overlapping ranges for set_regions() ---
> commit 696ade5451511d51ec415451a2df25bef4d15e9d
> Author: SJ Park <sj@kernel.org>
> 
> mm/damon/tests/core-kunit: test overlapping ranges for set_regions()
> 
> This commit adds a kunit test case to verify that passing overlapping input
> ranges to damon_set_regions() is properly disallowed.
> 
> > diff --git a/mm/damon/tests/core-kunit.h b/mm/damon/tests/core-kunit.h
> > index ac15393a7935b..3041b8288ec26 100644
> > --- a/mm/damon/tests/core-kunit.h
> > +++ b/mm/damon/tests/core-kunit.h
> > @@ -606,6 +606,17 @@ static void damon_test_set_regions(struct kunit *test)
> >  			{.start = 42, .end = 21},
> >  			}, 1, 1,
> >  			(struct damon_addr_range[]){}, 0, -EINVAL);
> > +	/*
> > +	 * Regions resulting in same region after alingment should return
>                                                   ^^^^^^^^^
> 
> [Severity: Low]
> This isn't a bug, but there is a typo here (alingment instead of alignment).

Thank you, I will fix.

> 
> > +	 * -EINVAL.
> > +	 */
> > +	damon_test_set_regions_for(test,
> > +			(struct damon_addr_range[]){}, 0,
> > +			(struct damon_addr_range[]){
> > +			{.start = 10, .end = 20},
> > +			{.start = 20, .end = 30},
> > +			}, 2, 4096,
> > +			(struct damon_addr_range[]){}, 0, -EINVAL);
> >  }
> >  
> >  static void damon_test_update_monitoring_result(struct kunit *test)
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260729033751.131213-1-sj@kernel.org?part=6


Thanks,
SJ

  reply	other threads:[~2026-07-29  3:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  3:37 [RFC PATCH v1.1 00/10] mm/damon: cleanup code, add test cases, and update guidances in docs SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 01/10] mm/damon/core: use damon_nr_samples_per_aggr() for max merge threshold SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 02/10] mm/damon/core: remove debug messages SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 03/10] mm/damon/vaddr: remove a debug message SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 04/10] mm/damon/tests/core-kunit: extend set_regions() test for error case SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 05/10] mm/damon/tests/core-kunit: test <=0 size damon_set_regions() inputs SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 06/10] mm/damon/tests/core-kunit: test overlapping ranges for set_regions() SJ Park
2026-07-29  3:48   ` sashiko-bot
2026-07-29  3:56     ` SJ Park [this message]
2026-07-29  3:37 ` [RFC PATCH v1.1 07/10] mm/damon/tests/core-kunit: test damon_nr_samples_per_aggr() SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 08/10] selftests/damon/sysfs.sh: test hugepage_mem_bp quota goal SJ Park
2026-07-29  3:45   ` sashiko-bot
2026-07-29  3:57     ` SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 09/10] Docs/mm/damon/maintainer-profile: update AI review for Sashiko replies SJ Park
2026-07-29  3:37 ` [RFC PATCH v1.1 10/10] Docs/ABI/damon: recommend subsystem doc instead of admin-guide SJ Park

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260729035613.131661-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=sashiko-bot@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox