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.7-rc4
Date: Tue, 28 Nov 2023 18:32:56 +0100 [thread overview]
Message-ID: <cover.1701191460.git.dsterba@suse.com> (raw)
Hi,
there are a few fixes and message updates. Please pull, thanks.
- fixes:
- for simple quotas, handle the case when a snapshot is created and
the target qgroup already exists
- fix a warning when file descriptor given to send ioctl is not writable
- fix off-by-one condition when checking chunk maps
- free pages when page array allocation fails during compression read,
other cases were handled
- fix memory leak on error handling path in ref-verify debugging feature
- copy missing struct member 'version' in 64/32bit compat send ioctl
- other updates
- tree-checker verifies inline backref ordering
- print messages to syslog on first mount and last unmount
- update error messages when reading chunk maps
----------------------------------------------------------------
The following changes since commit d3933152442b7f94419e9ea71835d71b620baf0e:
btrfs: make OWNER_REF_KEY type value smallest among inline refs (2023-11-09 14:02:12 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.7-rc3-tag
for you to fetch changes up to 0ac1d13a55eb37d398b63e6ff6db4a09a2c9128c:
btrfs: send: ensure send_fd is writable (2023-11-24 18:50:53 +0100)
----------------------------------------------------------------
Bragatheswaran Manickavel (1):
btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
David Sterba (1):
btrfs: fix 64bit compat send ioctl arguments not initializing version member
Filipe Manana (2):
btrfs: fix off-by-one when checking chunk map includes logical address
btrfs: make error messages more clear when getting a chunk map
Jann Horn (1):
btrfs: send: ensure send_fd is writable
Qu Wenruo (4):
btrfs: tree-checker: add type and sequence check for inline backrefs
btrfs: do not abort transaction if there is already an existing qgroup
btrfs: add dmesg output for first mount and last unmount of a filesystem
btrfs: free the allocated memory if btrfs_alloc_page_array() fails
fs/btrfs/disk-io.c | 1 +
fs/btrfs/extent_io.c | 11 ++++++++---
fs/btrfs/ioctl.c | 1 +
fs/btrfs/ref-verify.c | 2 ++
fs/btrfs/send.c | 2 +-
fs/btrfs/super.c | 5 ++++-
fs/btrfs/transaction.c | 2 +-
fs/btrfs/tree-checker.c | 39 +++++++++++++++++++++++++++++++++++++++
fs/btrfs/volumes.c | 9 +++++----
9 files changed, 62 insertions(+), 10 deletions(-)
next reply other threads:[~2023-11-28 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 17:32 David Sterba [this message]
2023-11-28 19:36 ` [GIT PULL] Btrfs fixes for 6.7-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.1701191460.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.