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 5.16-rc5
Date: Fri, 10 Dec 2021 21:41:43 +0100 [thread overview]
Message-ID: <cover.1638975228.git.dsterba@suse.com> (raw)
Hi,
a few more regression fixes and stable patches, mostly one-liners.
Please pull, thanks.
Regression fixes:
- fix pointer/ERR_PTR mismatch returned from memdup_user
- reset dedicated zoned mode relocation block group to avoid using it
and filling it without any recourse
Fixes:
- handle a case to FITRIM range (also to make fstests/generic/260 work)
- fix warning when extent buffer state and pages get out of sync after
an IO error
- fix transaction abort when syncing due to missing mapping error set on
metadata inode after inlining a compressed file
- fix transaction abort due to tree-log and zoned mode interacting in an
unexpected way
- fix memory leak of additional extent data when qgroup reservation
fails
- do proper handling of slot search call when deleting root refs
----------------------------------------------------------------
The following changes since commit daf87e953527b03c0bd4c0f41d704ba71186256d:
btrfs: fix the memory leak caused in lzo_compress_pages() (2021-11-26 16:10:05 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.16-rc4-tag
for you to fetch changes up to 8289ed9f93bef2762f9184e136d994734b16d997:
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling (2021-12-08 15:45:27 +0100)
----------------------------------------------------------------
Dan Carpenter (1):
btrfs: fix error pointer dereference in btrfs_ioctl_rm_dev_v2()
Johannes Thumshirn (2):
btrfs: free exchange changeset on failures
btrfs: zoned: clear data relocation bg on zone finish
Josef Bacik (3):
btrfs: fail if fstrim_range->start == U64_MAX
btrfs: clear extent buffer uptodate when we fail to write it
btrfs: call mapping_set_error() on btree inode with a write error
Naohiro Aota (1):
btrfs: fix re-dirty process of tree-log nodes
Qu Wenruo (1):
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
fs/btrfs/delalloc-space.c | 12 +++++++++---
fs/btrfs/extent-tree.c | 3 +++
fs/btrfs/extent_io.c | 14 ++++++++++++++
fs/btrfs/ioctl.c | 6 ++----
fs/btrfs/root-tree.c | 3 ++-
fs/btrfs/tree-log.c | 5 +++--
fs/btrfs/zoned.c | 2 ++
7 files changed, 35 insertions(+), 10 deletions(-)
next reply other threads:[~2021-12-10 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 20:41 David Sterba [this message]
2021-12-11 1:38 ` [GIT PULL] Btrfs fixes for 5.16-rc5 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.1638975228.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).