[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68866f17-f327-4df8-ae17-dfcc50362d4a@stanley.mountain>
Date: Tue, 29 Oct 2024 11:19:24 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Philip Li <philip.li@...el.com>
Cc: Matthew Sakai <msakai@...hat.com>, oe-kbuild@...ts.linux.dev,
Mike Snitzer <snitzer@...nel.org>, lkp@...el.com,
oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: drivers/md/dm-vdo/data-vio.c:976 vdo_launch_bio() warn:
inconsistent returns '&pool->lock'.
On Tue, Oct 29, 2024 at 11:07:07AM +0300, Dan Carpenter wrote:
> 3) The kbuild bot detected the bug, but unfortunately the cross function DB
> doesn't scale well enough for the kbuild bot to use so it didn't detect the
> fix.
Aw crud. It does still print a warning on linux-next actually.
Smatch says that we lock "&pool->lock" and unlocked
"&pool->discard_limiter->pool->lock".
Anyway. Points 1 and 4 that we were running new checks on old code and that
the code in the email did have a bug are correct.
regards,
dan carpenter
Powered by blists - more mailing lists