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.2-rc3
Date: Mon, 2 Jan 2023 13:38:50 +0100 [thread overview]
Message-ID: <cover.1672662506.git.dsterba@suse.com> (raw)
Hi,
first batch of regression and regular fixes. Please pull, thanks.
- regressions:
- fix error handling after conversion to qstr for paths
- fix raid56/scrub recovery caused by uninitialized variable after
conversion to error bitmaps
- restore qgroup backref lookup behaviour after recent refactoring
- fix leak of device lists at module exit time
- fix resolving backrefs for inline extent followed by prealloc
- reset defrag ioctl buffer on memory allocation error
----------------------------------------------------------------
The following changes since commit b7af0635c87ff78d6bd523298ab7471f9ffd3ce5:
btrfs: print transaction aborted messages with an error level (2022-12-05 18:00:59 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.2-rc2-tag
for you to fetch changes up to fee4c19937439693f2420a916169d08e88576e8e:
btrfs: fix fscrypt name leak after failure to join log transaction (2022-12-20 19:43:47 +0100)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: fix resolving backrefs for inline extent followed by prealloc
Christophe JAILLET (2):
btrfs: fix an error handling path in btrfs_rename()
btrfs: fix an error handling path in btrfs_defrag_leaves()
Filipe Manana (2):
btrfs: fix leak of fs devices after removing btrfs module
btrfs: fix fscrypt name leak after failure to join log transaction
Josef Bacik (2):
btrfs: restore BTRFS_SEQ_LAST when looking up qgroup backref lookup
btrfs: scrub: fix uninitialized return value in recover_scrub_rbio
Naohiro Aota (1):
btrfs: fix trace event name typo for FLUSH_DELAYED_REFS
fs/btrfs/backref.c | 4 ++++
fs/btrfs/defrag.c | 6 ++++--
fs/btrfs/inode.c | 6 ++++--
fs/btrfs/qgroup.c | 1 +
fs/btrfs/raid56.c | 2 +-
fs/btrfs/super.c | 1 +
fs/btrfs/tree-log.c | 5 ++++-
include/trace/events/btrfs.h | 2 +-
8 files changed, 20 insertions(+), 7 deletions(-)
next reply other threads:[~2023-01-02 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 12:38 David Sterba [this message]
2023-01-02 19:11 ` [GIT PULL] Btrfs fixes for 6.2-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.1672662506.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.