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.1-rc5
Date: Thu, 10 Nov 2022 16:29:36 +0100 [thread overview]
Message-ID: <cover.1668091779.git.dsterba@suse.com> (raw)
Hi,
a few more regression fixes and regular fixes. Please pull, thanks.
- revert memory optimization for scrub blocks, this misses errors in
2nd and following blocks
- add exception for ENOMEM as reason for transaction abort to not print
stack trace, syzbot has reported many
- zoned fixes:
- fix locking imbalance during scrub
- initialize zones for seeding device
- initialize zones for cloned device structures
- when looking up device, change assertion to a real check as some of
the search parameters can be passed by ioctl, reported by syzbot
- fix error pointer check in self tests
----------------------------------------------------------------
The following changes since commit eb81b682b131642405a05c627ab08cf0967b3dd8:
btrfs: fix inode reserve space leak due to nowait buffered write (2022-11-02 17:44:45 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.1-rc4-tag
for you to fetch changes up to c62f6bec53e63b11112e1ebce6bbaa39ce6f6706:
btrfs: zoned: fix locking imbalance on scrub (2022-11-07 14:35:25 +0100)
----------------------------------------------------------------
David Sterba (1):
btrfs: don't print stack trace when transaction is aborted due to ENOMEM
Johannes Thumshirn (3):
btrfs: zoned: clone zoned device info when cloning a device
btrfs: zoned: initialize device's zone info for seeding
btrfs: zoned: fix locking imbalance on scrub
Liu Shixin (1):
btrfs: fix match incorrectly in dev_args_match_device
Qu Wenruo (1):
Revert "btrfs: scrub: use larger block size for data extent scrub"
Zhang Xiaoxu (1):
btrfs: selftests: fix wrong error check in btrfs_free_dummy_root()
fs/btrfs/ctree.c | 16 ++++++++++++++++
fs/btrfs/ctree.h | 11 +++++++----
fs/btrfs/disk-io.c | 4 +++-
fs/btrfs/scrub.c | 9 +--------
fs/btrfs/tests/btrfs-tests.c | 2 +-
fs/btrfs/volumes.c | 39 +++++++++++++++++++++++++++++----------
fs/btrfs/volumes.h | 2 +-
fs/btrfs/zoned.c | 40 ++++++++++++++++++++++++++++++++++++++++
fs/btrfs/zoned.h | 11 +++++++++++
9 files changed, 109 insertions(+), 25 deletions(-)
next reply other threads:[~2022-11-10 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 15:29 David Sterba [this message]
2022-11-10 17:03 ` [GIT PULL] Btrfs fixes for 6.1-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.1668091779.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.