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.12-rc4
Date: Wed, 16 Oct 2024 16:26:39 +0200 [thread overview]
Message-ID: <cover.1729087733.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch with a few fixes, thanks.
- regression fix, dirty extents tracked in xarray for qgroups must be
adjusted for 32bit platforms
- fix potentially freeing uninitialized name in fscrypt structure
- fix warning about unneeded variable in a send callback
----------------------------------------------------------------
The following changes since commit e761be2a0744086fc4793a4870d4b5746b7fe8cd:
btrfs: fix clear_dirty and writeback ordering in submit_one_sector() (2024-10-09 13:23:51 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.12-rc3-tag
for you to fetch changes up to 2ab5e243c2266c841e0f6904fad1514b18eaf510:
btrfs: fix uninitialized pointer free on read_alloc_one_name() error (2024-10-11 19:55:04 +0200)
----------------------------------------------------------------
Christian Heusel (1):
btrfs: send: cleanup unneeded return variable in changed_verity()
Filipe Manana (1):
btrfs: use sector numbers as keys for the dirty extents xarray
Roi Martin (2):
btrfs: fix uninitialized pointer free in add_inode_ref()
btrfs: fix uninitialized pointer free on read_alloc_one_name() error
fs/btrfs/delayed-ref.c | 15 ++++++++-------
fs/btrfs/delayed-ref.h | 10 +++++++++-
fs/btrfs/qgroup.c | 21 ++++++++++++++++-----
fs/btrfs/send.c | 4 +---
fs/btrfs/tree-log.c | 6 +++---
5 files changed, 37 insertions(+), 19 deletions(-)
next reply other threads:[~2024-10-16 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 14:26 David Sterba [this message]
2024-10-16 20:51 ` [GIT PULL] Btrfs fixes for 6.12-rc4 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.1729087733.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.