From: Bill O'Donnell <bodonnel@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: cmaiolino@redhat.com, Bill O'Donnell <bodonnel@redhat.com>
Subject: [PATCH 3/4] xfs_fsr: correct type in fsrprintf() call
Date: Thu, 13 Jun 2024 13:07:07 -0500 [thread overview]
Message-ID: <20240613181745.1052423-4-bodonnel@redhat.com> (raw)
In-Reply-To: <20240613181745.1052423-1-bodonnel@redhat.com>
Use %ld instead of %d for howlong variable.
Coverity-id: 1596598
Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
---
fsr/xfs_fsr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fsr/xfs_fsr.c b/fsr/xfs_fsr.c
index fdd37756..d204e3a4 100644
--- a/fsr/xfs_fsr.c
+++ b/fsr/xfs_fsr.c
@@ -426,7 +426,7 @@ fsrallfs(char *mtab, time_t howlong, char *leftofffile)
fsdesc_t *fsp;
struct stat sb, sb2;
- fsrprintf("xfs_fsr -m %s -t %d -f %s ...\n", mtab, howlong, leftofffile);
+ fsrprintf("xfs_fsr -m %s -t %ld -f %s ...\n", mtab, howlong, leftofffile);
endtime = starttime + howlong;
fs = fsbase;
--
2.45.2
next prev parent reply other threads:[~2024-06-13 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 18:07 [PATCH 0/4] xfsprogs: coverity fixes Bill O'Donnell
2024-06-13 18:07 ` [PATCH 1/4] mkfs.xfs: avoid potential overflowing expression in xfs_mkfs.c Bill O'Donnell
2024-06-13 18:35 ` Christoph Hellwig
2024-06-13 18:07 ` [PATCH 2/4] xfs_db: fix unitialized variable ifake->if_levels Bill O'Donnell
2024-06-13 18:36 ` Christoph Hellwig
2024-06-13 18:58 ` Bill O'Donnell
2024-06-13 18:07 ` Bill O'Donnell [this message]
2024-06-13 18:37 ` [PATCH 3/4] xfs_fsr: correct type in fsrprintf() call Christoph Hellwig
2024-06-13 18:07 ` [PATCH 4/4] xfs_repair: correct type of variable global_msgs.interval to time_t Bill O'Donnell
2024-06-13 18:38 ` Christoph Hellwig
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=20240613181745.1052423-4-bodonnel@redhat.com \
--to=bodonnel@redhat.com \
--cc=cmaiolino@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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