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.10-rc2
Date: Fri, 30 Oct 2020 17:12:27 +0100 [thread overview]
Message-ID: <cover.1604073247.git.dsterba@suse.com> (raw)
Hi,
please pull the following branch with fixes. Thanks.
- lockdep fixes
- drop path locks before manipulating sysfs objects or qgroups
- preliminary fixes before tree locks get switched to rwsem
- use annotated seqlock
- build warning fixes (printk format)
- fix relocation vs fallocate race
- tree checker properly validates number of stripes and parity
- readahead vs device replace fixes
- iomap dio fix for unnecessary buffered io fallback
----------------------------------------------------------------
The following changes since commit 1fd4033dd011a3525bacddf37ab9eac425d25c4f:
btrfs: rename BTRFS_INODE_ORDERED_DATA_CLOSE flag (2020-10-07 12:18:00 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.10-rc1-tag
for you to fetch changes up to d5c8238849e7bae6063dfc16c08ed62cee7ee688:
btrfs: convert data_seqcount to seqcount_mutex_t (2020-10-27 15:11:51 +0100)
----------------------------------------------------------------
Daniel Xu (1):
btrfs: tree-checker: validate number of chunk stripes and parity
Davidlohr Bueso (1):
btrfs: convert data_seqcount to seqcount_mutex_t
Filipe Manana (3):
btrfs: fix relocation failure due to race with fallocate
btrfs: fix use-after-free on readahead extent after failure to create it
btrfs: fix readahead hang and use-after-free after removing a device
Johannes Thumshirn (1):
btrfs: don't fallback to buffered read if we don't need to
Josef Bacik (3):
btrfs: drop the path before adding block group sysfs files
btrfs: drop the path before adding qgroup items when enabling qgroups
btrfs: add a helper to read the tree_root commit root for backref lookup
Pujin Shi (1):
btrfs: tree-checker: fix incorrect printk format
fs/btrfs/backref.c | 13 ++++-
fs/btrfs/block-group.c | 1 +
fs/btrfs/ctree.h | 2 +
fs/btrfs/dev-replace.c | 5 ++
fs/btrfs/disk-io.c | 139 ++++++++++++++++++++++++++++++++++--------------
fs/btrfs/disk-io.h | 3 ++
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/file.c | 3 +-
fs/btrfs/inode.c | 8 ++-
fs/btrfs/qgroup.c | 18 +++++++
fs/btrfs/reada.c | 47 ++++++++++++++++
fs/btrfs/tree-checker.c | 18 +++++++
fs/btrfs/volumes.c | 5 +-
fs/btrfs/volumes.h | 12 ++---
14 files changed, 225 insertions(+), 51 deletions(-)
next reply other threads:[~2020-10-30 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 16:12 David Sterba [this message]
2020-10-30 20:35 ` [GIT PULL] Btrfs fixes for 5.10-rc2 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.1604073247.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