From: Damien Le Moal <dlemoal@kernel.org>
To: Dan Carpenter <error27@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: linux-block@vger.kernel.org, ZHOU Jiaxiang <me@fxti.xyz>
Subject: Re: [bug report] Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git
Date: Tue, 22 Sep 2026 12:16:51 +0900 [thread overview]
Message-ID: <632cc6ac-94b9-4cb6-a589-0a81f62bc38a@kernel.org> (raw)
In-Reply-To: <arGDF5byCiew-pqQ@stanley.mountain>
On 9/22/26 04:18, Dan Carpenter wrote:
> Hello Mark Brown,
>
> Commit a9ce2250a714 ("Merge branch 'for-next' of
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git")
> from Sep 18, 2026 (linux-next), leads to the following Smatch static
> checker warning:
>
> block/blk-zoned.c:2200 disk_init_revalidate_args()
> warn: impossible condition '(args->nr_zones > (~0)) => (0-u32max > u32max)'
>
> block/blk-zoned.c
> 2195 static int disk_init_revalidate_args(struct gendisk *disk,
> 2196 struct blk_revalidate_zone_args *args)
> 2197 {
> 2198 args->disk = disk;
> 2199 args->nr_zones = disk_get_nr_zones(disk, args->capacity);
> --> 2200 if (args->nr_zones > UINT_MAX)
> ^^^^^^^^^^^^^^^^^^^^^^^^^
This was fixed with an improved conflict resolution yesterday. Today's
linux-next does not have this anymore, so this should now be all good.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2026-09-22 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 19:18 [bug report] Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git Dan Carpenter
2026-09-22 3:16 ` Damien Le Moal [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=632cc6ac-94b9-4cb6-a589-0a81f62bc38a@kernel.org \
--to=dlemoal@kernel.org \
--cc=broonie@kernel.org \
--cc=error27@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=me@fxti.xyz \
/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