linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	syzbot+841a46899768ec7bec67@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/damon/core: fix divide error in damon_nr_accesses_to_accesses_bp()
Date: Fri, 26 May 2023 19:31:49 -0700	[thread overview]
Message-ID: <20230527023149.8441-1-sj@kernel.org> (raw)
In-Reply-To: <20230527023330.23535-1-wangkefeng.wang@huawei.com>

Hi Kefeng,

Thank you so much for this awesome patch!

On Sat, 27 May 2023 10:33:30 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:

> If 'aggr_interval' is smaller than 'sample_interval', max_nr_accesses becomes
> zero which leads to divide error in damon_nr_accesses_to_accesses_bp(), let's
> validate the values of them in damon_set_attrs() to fix it, which similar to
> others attrs check.
> 
> Reported-by: syzbot+841a46899768ec7bec67@syzkaller.appspotmail.com

I think it would be good to add the link to the report, e.g.,
"Link: https://lore.kernel.org/damon/00000000000055fc4e05fc975bc2@google.com/"

> Fixes: 2f5bef5a590b ("mm/damon/core: update monitoring results for new monitoring attributes")

Could you please add 'Cc: <stable@vger.kernel.org> # 6.3.x-' ?

Also, checkpatch.pl raises below warnings.

```
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#61: 
If 'aggr_interval' is smaller than 'sample_interval', max_nr_accesses becomes

WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#66: 
Reported-by: syzbot+841a46899768ec7bec67@syzkaller.appspotmail.com
Fixes: 2f5bef5a590b ("mm/damon/core: update monitoring results for new monitoring attributes")

total: 0 errors, 2 warnings, 8 lines checked
```

Could you please resolve those by wrapping the commit messages and adding
'Closes:' tag?  'Closes:' tag might be able to replace the 'Link:' tag I
supposed above.  I have no strong opinions there but having both may harm
nothing.

Other than those,

Reviewed-by: SeongJae Park <sj@kernel.org>


Thanks,
SJ

> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
>  mm/damon/core.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/mm/damon/core.c b/mm/damon/core.c
> index d9ef62047bf5..91cff7f2997e 100644
> --- a/mm/damon/core.c
> +++ b/mm/damon/core.c
> @@ -551,6 +551,8 @@ int damon_set_attrs(struct damon_ctx *ctx, struct damon_attrs *attrs)
>  		return -EINVAL;
>  	if (attrs->min_nr_regions > attrs->max_nr_regions)
>  		return -EINVAL;
> +	if (attrs->sample_interval > attrs->aggr_interval)
> +		return -EINVAL;
>  
>  	damon_update_monitoring_results(ctx, attrs);
>  	ctx->attrs = *attrs;
> -- 
> 2.35.3
> 


  reply	other threads:[~2023-05-27  2:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27  2:33 Kefeng Wang
2023-05-27  2:31 ` SeongJae Park [this message]
2023-05-27  2:34   ` SeongJae 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=20230527023149.8441-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+841a46899768ec7bec67@syzkaller.appspotmail.com \
    --cc=wangkefeng.wang@huawei.com \
    /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