mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Xiaolei <xiaoleiwangxiaolei@gmail.com>
To: SJ Park <sj@kernel.org>
Cc: jm5905938@gmail.com, akpm@linux-foundation.org, david@kernel.org,
	ljs@kernel.org, error27@gmail.com, damon@lists.linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, "Liam R. Howlett" <liam@infradead.org>,
	Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Vlastimil Babka <vbabka@kernel.org>
Subject: Re: [PATCH] mm/damon/core: reject empty access pattern intervals on scheme commit
Date: Thu, 5 Nov 2026 09:45:10 +0800	[thread overview]
Message-ID: <0ee661a9-b642-424f-99a1-21c9731c53aa@gmail.com> (raw)
In-Reply-To: <20261105013653.88123-1-sj@kernel.org>


在 2026/11/5 9:36, SJ Park 写道:
> On Wed, 4 Nov 2026 09:17:24 +0800 Wang Xiaolei <xiaoleiwangxiaolei@gmail.com> wrote:
>
>> Hi SeongJae and Aveline
>>
>>    Thank you both for the careful review.
>>
>> I appreciate the clarification that DAMON simply executes what
>>
>>    the user configured, and that this is more of an input validation
>>
>> improvement than a bug fix. Perhaps I was too aggressive in framing
>>
>> it as a bug.
> Thank you for clarifying.  But my point is that this change might be just
> unnecessary behavior change rather than an improvement.  What do you think?
Hi SeongJae

Thank you again for the clear explanation.

I agree with you . My earlier framing was wrong;

I won't push this patch further. Let me focus on the

other items that are genuine bugs instead.

thanks

xiaolei

>
>
> Thanks,
> SJ
>
> [...]

      reply	other threads:[~2026-11-05  1:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 10:54 Xiaolei Wang (Kaihong)
2026-11-03 11:44 ` Aveline Noir
2026-11-03 14:53 ` SJ Park
2026-11-04  1:17   ` Wang Xiaolei
2026-11-05  1:36     ` SJ Park
2026-11-05  1:45       ` Wang Xiaolei [this message]

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=0ee661a9-b642-424f-99a1-21c9731c53aa@gmail.com \
    --to=xiaoleiwangxiaolei@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=error27@gmail.com \
    --cc=jm5905938@gmail.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@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
all inboxes | Powered by JetHome®