From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.18-rc2
Date: Tue, 5 Apr 2022 13:28:27 +0200 [thread overview]
Message-ID: <cover.1649109877.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes for btrfs, thanks.
- prevent deleting subvolume with active swapfile
- fix qgroup reserve limit calculation overflow
- remove device count in superblock and its item in one transaction so
they cant't get out of sync
- skip defragmenting an isolated sector, this could cause some extra IO
- unify handling of mtime/permissions in hole punch with fallocate
- zoned mode fixes:
- remove assert checking for only single mode, we have the DUP mode
implemented
- fix potential lockdep warning while traversing devices when checking
for zone activation
----------------------------------------------------------------
The following changes since commit d3e29967079c522ce1c5cab0e9fab2c280b977eb:
btrfs: zoned: put block group after final usage (2022-03-14 13:13:54 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.18-rc1-tag
for you to fetch changes up to 60021bd754c6ca0addc6817994f20290a321d8d6:
btrfs: prevent subvol with swapfile from being deleted (2022-03-24 17:50:57 +0100)
----------------------------------------------------------------
Darrick J. Wong (1):
btrfs: fix fallocate to use file_modified to update permissions consistently
Ethan Lien (1):
btrfs: fix qgroup reserve overflow the qgroup limit
Johannes Thumshirn (2):
btrfs: zoned: traverse devices under chunk_mutex in btrfs_can_activate_zone
btrfs: zoned: remove left over ASSERT checking for single profile
Josef Bacik (1):
btrfs: do not warn for free space inode in cow_file_range
Kaiwen Hu (1):
btrfs: prevent subvol with swapfile from being deleted
Qu Wenruo (2):
btrfs: remove device item and update super block in the same transaction
btrfs: avoid defragging extents whose next extents are not targets
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/file.c | 13 +++++++++--
fs/btrfs/inode.c | 23 ++++++++++++++++++-
fs/btrfs/ioctl.c | 20 +++++++++++-----
fs/btrfs/volumes.c | 65 ++++++++++++++++++++++------------------------------
fs/btrfs/zoned.c | 13 ++++-------
6 files changed, 81 insertions(+), 55 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
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.18-rc2
Date: Tue, 5 Apr 2022 15:24:47 +0200 [thread overview]
Message-ID: <cover.1649109877.git.dsterba@suse.com> (raw)
Message-ID: <20220405132447.-UxNZrBWqrtLokNqO5q7mpVic4cU7rlHxRimzayqReE@z> (raw)
Hi,
please pull the following fixes for btrfs, thanks.
- prevent deleting subvolume with active swapfile
- fix qgroup reserve limit calculation overflow
- remove device count in superblock and its item in one transaction so
they cant't get out of sync
- skip defragmenting an isolated sector, this could cause some extra IO
- unify handling of mtime/permissions in hole punch with fallocate
- zoned mode fixes:
- remove assert checking for only single mode, we have the DUP mode
implemented
- fix potential lockdep warning while traversing devices when checking
for zone activation
----------------------------------------------------------------
The following changes since commit d3e29967079c522ce1c5cab0e9fab2c280b977eb:
btrfs: zoned: put block group after final usage (2022-03-14 13:13:54 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.18-rc1-tag
for you to fetch changes up to 60021bd754c6ca0addc6817994f20290a321d8d6:
btrfs: prevent subvol with swapfile from being deleted (2022-03-24 17:50:57 +0100)
----------------------------------------------------------------
Darrick J. Wong (1):
btrfs: fix fallocate to use file_modified to update permissions consistently
Ethan Lien (1):
btrfs: fix qgroup reserve overflow the qgroup limit
Johannes Thumshirn (2):
btrfs: zoned: traverse devices under chunk_mutex in btrfs_can_activate_zone
btrfs: zoned: remove left over ASSERT checking for single profile
Josef Bacik (1):
btrfs: do not warn for free space inode in cow_file_range
Kaiwen Hu (1):
btrfs: prevent subvol with swapfile from being deleted
Qu Wenruo (2):
btrfs: remove device item and update super block in the same transaction
btrfs: avoid defragging extents whose next extents are not targets
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/file.c | 13 +++++++++--
fs/btrfs/inode.c | 23 ++++++++++++++++++-
fs/btrfs/ioctl.c | 20 +++++++++++-----
fs/btrfs/volumes.c | 65 ++++++++++++++++++++++------------------------------
fs/btrfs/zoned.c | 13 ++++-------
6 files changed, 81 insertions(+), 55 deletions(-)
next reply other threads:[~2022-04-05 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 11:28 David Sterba [this message]
2022-04-05 13:24 ` [GIT PULL] Btrfs fixes for 5.18-rc2 David Sterba
2022-04-05 15:58 ` Linus Torvalds
2022-04-05 17:38 ` David Sterba
2022-04-06 6:08 ` Christoph Hellwig
2022-04-05 16:52 ` 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.1649109877.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