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-rc5
Date: Mon, 16 Jan 2023 15:45:40 +0100 [thread overview]
Message-ID: <cover.1673876631.git.dsterba@suse.com> (raw)
Hi,
another batch of fixes, dealing with fallouts from 6.1 reported by users.
One or two extra -rcs would be appreciated, this pull request is for rc5
which is my usual target for big changes code freeze but there are still
such branches in the queue.
Please pull, thanks.
- tree-log fixes
- fix directory logging due to race with concurrent index key deletion
- fix missing error handling when logging directory items
- handle case of conflicting inodes being added to the log
- remove transaction aborts for not so serious errors
- fix qgroup accounting warning when rescan can be started at time with
temporarily disable accounting
- print more specific errors to system log when device scan ioctl fails
- disable space overcommit for ZNS devices, causing heavy performance
drop
----------------------------------------------------------------
The following changes since commit 2ba48b20049b5a76f34a85f853c9496d1b10533a:
btrfs: fix compat_ro checks against remount (2023-01-03 16:22:13 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.2-rc4-tag
for you to fetch changes up to 09e44868f1e03c7825ca4283256abedc95e249a3:
btrfs: do not abort transaction on failure to update log root (2023-01-12 15:43:31 +0100)
----------------------------------------------------------------
Filipe Manana (5):
btrfs: fix missing error handling when logging directory items
btrfs: add missing setup of log for full commit at add_conflicting_inode()
btrfs: do not abort transaction on failure to write log tree when syncing log
btrfs: do not abort transaction on failure to update log root
Naohiro Aota (1):
btrfs: zoned: enable metadata over-commit for non-ZNS setup
Qu Wenruo (2):
btrfs: add extra error messages to cover non-ENOMEM errors from device_add_list()
btrfs: qgroup: do not warn on record without old_roots populated
fs/btrfs/disk-io.c | 9 ++++++++-
fs/btrfs/fs.h | 6 ++++++
fs/btrfs/qgroup.c | 14 ++++++++++++--
fs/btrfs/space-info.c | 3 ++-
fs/btrfs/tree-log.c | 47 +++++++++++++++++++++++++++++++----------------
fs/btrfs/volumes.c | 11 ++++++++++-
fs/btrfs/zoned.c | 2 ++
7 files changed, 71 insertions(+), 21 deletions(-)
next reply other threads:[~2023-01-16 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 14:45 David Sterba [this message]
2023-01-16 18:10 ` [GIT PULL] Btrfs fixes for 6.2-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.1673876631.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