[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNO+1evgD=Ty8YXT6_ac33vJKE=UaOE8ADzd57_YoZ83ag@mail.gmail.com>
Date: Mon, 24 Jun 2024 10:44:29 +0200
From: Marco Elver <elver@...gle.com>
To: Thorsten Blum <thorsten.blum@...lux.com>
Cc: dvyukov@...gle.com, kasan-dev@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kcsan: Use min() to fix Coccinelle warning
On Mon, 24 Jun 2024 at 10:00, Thorsten Blum <thorsten.blum@...lux.com> wrote:
>
> On 24. Jun 2024, at 00:02, Marco Elver <elver@...gle.com> wrote:
> > On Mon, 24 Jun 2024 at 00:08, Thorsten Blum <thorsten.blum@...lux.com> wrote:
> >>
> >> Fixes the following Coccinelle/coccicheck warning reported by
> >> minmax.cocci:
> >>
> >> WARNING opportunity for min()
> >>
> >> Use size_t instead of int for the result of min().
> >>
> >> Signed-off-by: Thorsten Blum <thorsten.blum@...lux.com>
> >
> > Reviewed-by: Marco Elver <elver@...gle.com>
> >
> > Thanks for polishing (but see below). Please compile-test with
> > CONFIG_KCSAN=y if you haven't.
>
> Yes, I compile-tested it with CONFIG_KCSAN=y, but forgot to mention it.
>
> > While we're here polishing things this could be:
> >
> > const size_t read_len = min(count, sizeof(kbuf) - 1);
> >
> > ( +const, remove redundant () )
>
> Should I submit a v2 or are you adding this already?
Sending a v2 is cleaner, and also Cc Paul E. McKenney
<paulmck@...nel.org>, because the KCSAN patches go through the -rcu
kernel tree.
Thanks,
-- Marco
Powered by blists - more mailing lists