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-rc6
Date: Fri, 17 Dec 2021 22:19:27 +0100 [thread overview]
Message-ID: <cover.1639775076.git.dsterba@suse.com> (raw)
Hi,
still there are a few more fixes, almost all error handling one-liners
and for stable. Please pull, thanks.
* regression fix in directory logging items
* regression fix of extent buffer status bits handling after an error
* fix memory leak in error handling path in tree-log
* fix freeing invalid anon device number when handling errors during
subvolume creation
* fix warning when freeing leaf after subvolume creation failure
* fix missing blkdev put in device scan error handling
* fix invalid delayed ref after subvolume creation failure
----------------------------------------------------------------
The following changes since commit 8289ed9f93bef2762f9184e136d994734b16d997:
btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling (2021-12-08 15:45:27 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.16-rc5-tag
for you to fetch changes up to 4989d4a0aed3fb30f5b48787a689d7090de6f86d:
btrfs: fix missing blkdev_put() call in btrfs_scan_one_device() (2021-12-15 17:07:34 +0100)
----------------------------------------------------------------
Filipe Manana (4):
btrfs: fix double free of anon_dev after failure to create subvolume
btrfs: fix missing last dir item offset update when logging directory
btrfs: fix invalid delayed ref after subvolume creation failure
btrfs: fix warning when freeing leaf after subvolume creation failure
Jianglei Nie (1):
btrfs: fix memory leak in __add_inode_ref()
Josef Bacik (1):
btrfs: check WRITE_ERR when trying to read an extent buffer
Shin'ichiro Kawasaki (1):
btrfs: fix missing blkdev_put() call in btrfs_scan_one_device()
fs/btrfs/ctree.c | 17 +++++++++--------
fs/btrfs/ctree.h | 7 ++++++-
fs/btrfs/disk-io.c | 8 ++++++++
fs/btrfs/extent-tree.c | 13 +++++++------
fs/btrfs/extent_io.c | 8 ++++++++
fs/btrfs/free-space-tree.c | 4 ++--
fs/btrfs/ioctl.c | 10 ++++++----
fs/btrfs/qgroup.c | 3 ++-
fs/btrfs/tree-log.c | 2 ++
fs/btrfs/volumes.c | 6 ++++--
10 files changed, 54 insertions(+), 24 deletions(-)
next reply other threads:[~2021-12-17 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 21:19 David Sterba [this message]
2021-12-17 22:21 ` [GIT PULL] Btrfs fixes for 5.16-rc6 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.1639775076.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