From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.11-rc3
Date: Wed, 7 Aug 2024 15:40:22 +0200 [thread overview]
Message-ID: <cover.1723037280.git.dsterba@suse.com> (raw)
Hi,
a few regular fixes. Please pull, thanks.
- fix double inode unlock for direct IO sync writes (reported by syzbot)
- fix root tree id/name map definitions, don't use fixed size buffers
for name (reported by -Werror=unterminated-string-initialization)
- fix qgroup reserve leaks in bufferd write path
- update scrub status structure more often so it can be reported in user
space more accurately and let 'resume' not repeat work
- in preparation to remove space chache v1 in the future print a warning
if it's detected
----------------------------------------------------------------
The following changes since commit b8e947e9f64cac9df85a07672b658df5b2bcff07:
btrfs: initialize location to fix -Wmaybe-uninitialized in btrfs_lookup_dentry() (2024-07-30 15:33:06 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.11-rc2-tag
for you to fetch changes up to 12653ec36112ab55fa06c01db7c4432653d30a8d:
btrfs: avoid using fixed char array size for tree names (2024-08-02 22:44:27 +0200)
----------------------------------------------------------------
Boris Burkov (2):
btrfs: implement launder_folio for clearing dirty page reserve
btrfs: fix qgroup reserve leaks in cow_file_range
Filipe Manana (1):
btrfs: fix double inode unlock for direct IO sync writes
Josef Bacik (1):
btrfs: emit a warning about space cache v1 being deprecated
Qu Wenruo (3):
btrfs: factor out stripe length calculation into a helper
btrfs: scrub: update last_physical after scrubbing one stripe
btrfs: avoid using fixed char array size for tree names
fs/btrfs/file.c | 5 ++++-
fs/btrfs/inode.c | 10 ++++++++++
fs/btrfs/print-tree.c | 2 +-
fs/btrfs/scrub.c | 25 +++++++++++++++++++------
fs/btrfs/super.c | 5 ++++-
5 files changed, 38 insertions(+), 9 deletions(-)
next reply other threads:[~2024-08-07 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 13:40 David Sterba [this message]
2024-08-07 17:02 ` [GIT PULL] Btrfs fixes for 6.11-rc3 pr-tracker-bot
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.1723037280.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.