From: Damien Le Moal <dlemoal@kernel.org>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>
Cc: naohiro.aota@wdc.com, jth@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zonefs: Fix the wrong format specifier
Date: Mon, 9 Dec 2024 08:17:38 +0900 [thread overview]
Message-ID: <901d37b0-d4c3-4ad2-b768-fc87d28c5a20@kernel.org> (raw)
In-Reply-To: <20241111054126.2929-1-zhujun2@cmss.chinamobile.com>
On 11/11/24 14:41, Zhu Jun wrote:
> The format specifier of "signed int" in snprintf() should be "%d", not
> "%u".
My apologies for the late reply.
A better fix is to make f "unsigned int" as that is consistent with
g_nr_zones and the fact that up to "unsigned int" total number of zones are
allowed for a zoned device.
Can you send a v2 ? Also please add a Fixes tag.
>
> Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
> ---
> fs/zonefs/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
> index faf1eb87895d..43c2f4a59b50 100644
> --- a/fs/zonefs/super.c
> +++ b/fs/zonefs/super.c
> @@ -811,7 +811,7 @@ static int zonefs_readdir_zgroup(struct file *file,
> for (f = ctx->pos - 2; f < zgroup->g_nr_zones; f++) {
> z = &zgroup->g_zones[f];
> ino = z->z_sector >> sbi->s_zone_sectors_shift;
> - fname_len = snprintf(fname, ZONEFS_NAME_MAX - 1, "%u", f);
> + fname_len = snprintf(fname, ZONEFS_NAME_MAX - 1, "%d", f);
> if (!dir_emit(ctx, fname, fname_len, ino, DT_REG))
> break;
> ctx->pos++;
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2024-12-08 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 5:41 Zhu Jun
2024-11-13 17:55 ` Chaitanya Kulkarni
2024-12-08 23:17 ` 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=901d37b0-d4c3-4ad2-b768-fc87d28c5a20@kernel.org \
--to=dlemoal@kernel.org \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=zhujun2@cmss.chinamobile.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
all inboxes | Powered by JetHome®