From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/3] btrfs-progs: a couple fixes
Date: Wed, 23 Aug 2023 10:27:47 -0400 [thread overview]
Message-ID: <cover.1692800798.git.josef@toxicpanda.com> (raw)
Hello,
These are a set of fixes that I needed for the ctree sync to work properly, and
one fix that was just broken in general. They apply cleanly to devel and should
be straightforward enough. Thanks,
Josef
Josef Bacik (3):
btrfs-progs: take a ref in the root locking code
btrfs-progs: clear root dirty when we update the root
btrfs-progs: fix improper error handling in btrfs filesystem usage
cmds/filesystem-usage.c | 8 +++-----
kernel-shared/locking.c | 3 +++
kernel-shared/transaction.c | 2 ++
3 files changed, 8 insertions(+), 5 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-23 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:27 Josef Bacik [this message]
2023-08-23 14:27 ` [PATCH 1/3] btrfs-progs: take a ref in the root locking code Josef Bacik
2023-08-23 14:27 ` [PATCH 2/3] btrfs-progs: clear root dirty when we update the root Josef Bacik
2023-08-23 17:17 ` David Sterba
2023-08-23 14:27 ` [PATCH 3/3] btrfs-progs: fix improper error handling in btrfs filesystem usage Josef Bacik
2023-08-23 17:18 ` [PATCH 0/3] btrfs-progs: a couple fixes 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.1692800798.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