From: Andrey Albershteyn <aalbersh@redhat.com>
To: cem@kernel.org, linux-xfs@vger.kernel.org
Cc: djwong@kernel.org, Andrey Albershteyn <aalbersh@redhat.com>
Subject: [PATCH v3 0/4] xfsprogs random fixes found by Coverity scan
Date: Wed, 17 Apr 2024 14:52:24 +0200 [thread overview]
Message-ID: <20240417125227.916015-2-aalbersh@redhat.com> (raw)
Hi all,
This is bunch of random fixes found by Coverity scan, there's memory
leak, truncation of time_t to int, access overflow, and freeing of
uninitialized struct.
v3:
- better error message for too long runtime
v2:
- remove parentheses
- drop count initialization patch as this code goes away with parent
pointers
- rename unload: label
- howlong limit
--
Andrey
Andrey Albershteyn (4):
xfs_db: fix leak in flist_find_ftyp()
xfs_repair: make duration take time_t
xfs_scrub: don't call phase_end if phase_rusage was not initialized
xfs_fsr: convert fsrallfs to use time_t instead of int
db/flist.c | 4 +++-
fsr/xfs_fsr.c | 10 ++++++++--
repair/globals.c | 2 +-
repair/globals.h | 2 +-
repair/progress.c | 7 ++++---
repair/progress.h | 2 +-
repair/xfs_repair.c | 2 +-
scrub/xfs_scrub.c | 3 ++-
8 files changed, 21 insertions(+), 11 deletions(-)
--
2.42.0
next reply other threads:[~2024-04-17 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 12:52 Andrey Albershteyn [this message]
2024-04-17 12:52 ` [PATCH v3 1/4] xfs_db: fix leak in flist_find_ftyp() Andrey Albershteyn
2024-04-17 15:20 ` Christoph Hellwig
2024-04-17 12:52 ` [PATCH v3 2/4] xfs_repair: make duration take time_t Andrey Albershteyn
2024-04-17 15:21 ` Christoph Hellwig
2024-04-17 12:52 ` [PATCH v3 3/4] xfs_scrub: don't call phase_end if phase_rusage was not initialized Andrey Albershteyn
2024-04-17 12:52 ` [PATCH v3 4/4] xfs_fsr: convert fsrallfs to use time_t instead of int Andrey Albershteyn
2024-04-17 15:19 ` Darrick J. Wong
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=20240417125227.916015-2-aalbersh@redhat.com \
--to=aalbersh@redhat.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).