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-rc6
Date: Fri, 27 Nov 2020 16:36:15 +0100 [thread overview]
Message-ID: <cover.1606490199.git.dsterba@suse.com> (raw)
Hi,
a few fixes for various warnings that accumulated over past two weeks.
- tree-checker: add missing return values for some errors
- lockdep fixes
- when reading qgroup config and starting quota rescan
- reverse order of quota ioctl lock and VFS freeze lock
- avoid accessing potentially stale fs info during device scan,
reported by syzbot
- add scope NOFS protection around qgroup relation changes
- check for running transaction before flushing qgroups
- fix tracking of new delalloc ranges for some cases
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit 468600c6ec28613b756193c5f780aac062f1acdf:
btrfs: ref-verify: fix memory leak in btrfs_ref_tree_mod (2020-11-05 13:03:39 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.10-rc5-tag
for you to fetch changes up to a855fbe69229078cd8aecd8974fb996a5ca651e6:
btrfs: fix lockdep splat when enabling and disabling qgroups (2020-11-23 21:16:43 +0100)
----------------------------------------------------------------
Daniel Xu (1):
btrfs: tree-checker: add missing return after error in root_item
David Sterba (1):
btrfs: tree-checker: add missing returns after data_ref alignment checks
Filipe Manana (4):
btrfs: fix missing delalloc new bit for new delalloc ranges
btrfs: fix lockdep splat when reading qgroup config on mount
btrfs: do nofs allocations when adding and removing qgroup relations
btrfs: fix lockdep splat when enabling and disabling qgroups
Johannes Thumshirn (1):
btrfs: don't access possibly stale fs_info data for printing duplicate device
Qu Wenruo (1):
btrfs: qgroup: don't commit transaction when we already hold the handle
fs/btrfs/ctree.h | 5 ++-
fs/btrfs/file.c | 57 ----------------------------
fs/btrfs/inode.c | 58 +++++++++++++++++++++++++++++
fs/btrfs/qgroup.c | 88 +++++++++++++++++++++++++++++++++++++++-----
fs/btrfs/tests/inode-tests.c | 12 ++++--
fs/btrfs/tree-checker.c | 3 ++
fs/btrfs/volumes.c | 8 +++-
7 files changed, 158 insertions(+), 73 deletions(-)
next reply other threads:[~2020-11-27 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 15:36 David Sterba [this message]
2020-11-27 21:21 ` [GIT PULL] Btrfs fixes for 5.10-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.1606490199.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;
as well as URLs for NNTP newsgroup(s).