On Sun, Oct 02, 2022 at 07:36:56PM +0000, SeongJae Park wrote: > Hi Hyeonggon, > > On Sun, 2 Oct 2022 16:24:29 +0900 Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx> wrote: > > > On Sun, Oct 02, 2022 at 01:24:23PM +0900, Hyeonggon Yoo wrote: > > > Hi guys, yesterday I just built and booted latest mm-everything, > > > and I got following report from KUNIT test. > > > > > > Environment: > > > - x86_64, gcc 11.2.0 > > > - mm-everything (tag: mm-everything-2022-10-01-01-55) > > > - config attached > > > > > > Report (stacktrace decoded): > > > > FYI, below is the bad commit from git bisection ;) > > > > Thanks! > > > > 065530b966a42d63f214ba40427dc8d00345f573 is the first bad commit > > commit 065530b966a42d63f214ba40427dc8d00345f573 > > Author: SeongJae Park <sj@xxxxxxxxxx> > > Date: Fri Sep 9 20:28:57 2022 +0000 > > > > mm/damon/core-test: test damon_set_regions > > > > Preceding commit fixes a bug in 'damon_set_regions()', which allows holes > > in the new monitoring target ranges. This commit adds a kunit test case > > for the problem to avoid any regression. > > Thank you so much for this kind report! I just sent a patch[1] for this. It > should fix this issue. You're welcome! Thank you for quickly fixing this. > BTW, please note that the real issue was there even > before the kunit commit, but the kunit commit was the first commit that > triggers the issue. Yeah, makes sense. Hmm.. Do you think it would be worth to backport to -stable? > [1] https://lore.kernel.org/damon/20221002193130.8227-1-sj@xxxxxxxxxx/ > -- Thanks, Hyeonggon
