From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2] Fix some -Wmaybe-uninitialized errors
Date: Tue, 5 Sep 2023 12:15:22 -0400 [thread overview]
Message-ID: <cover.1693930391.git.josef@toxicpanda.com> (raw)
Hello,
Jens reported to me two warnings he was seeing with
CONFIG_CC_OPTIMIZE_FOR_SIZE=y set in his .config. We don't see these errors
without this option, and they're not correct warnings. However we've had issues
where -Wmaybe-uninitialized would have caught a real bug, so this warning is
generally valuable. Fix these warnings so we have a clean build. Thanks,
Josef
Josef Bacik (2):
btrfs: make sure to initialize start and len in find_free_dev_extent
btrfs: initialize start_slot in btrfs_log_prealloc_extents
fs/btrfs/tree-log.c | 2 +-
fs/btrfs/volumes.c | 14 ++++++--------
2 files changed, 7 insertions(+), 9 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-05 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 16:15 Josef Bacik [this message]
2023-09-05 16:15 ` [PATCH 1/2] btrfs: make sure to initialize start and len in find_free_dev_extent Josef Bacik
2023-09-05 17:30 ` Jens Axboe
2023-09-05 22:48 ` Qu Wenruo
2023-09-06 16:13 ` David Sterba
2023-09-05 16:15 ` [PATCH 2/2] btrfs: initialize start_slot in btrfs_log_prealloc_extents Josef Bacik
2023-09-05 17:31 ` Jens Axboe
2023-09-05 22:51 ` Qu Wenruo
2023-09-06 16:17 ` David Sterba
2023-09-06 16:18 ` [PATCH 0/2] Fix some -Wmaybe-uninitialized errors David Sterba
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=cover.1693930391.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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