Skip to contentSkip to conversation

Btrfs fixes for 5.18-rc2

GIT PULL Merged David Sterba 5 participants 5 messages Apr 5, 2022 – Apr 6, 2022 Btrfs file system

lore
Share & tools
lore

David Sterba

author maintainer
#0 lore 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(-)
#2 lore raw
In reply to David Sterba
Quoted 2 lines · David Sterba

please pull the following fixes for btrfs, thanks.

Hmm. I got two copies of this...

...and both were in my spam folder.

I don't see anything wrong with the message (spf and dkim both fine).so I assume it's something about suse.sz or suse.de that gmail doesn't like. Presumably some spammer sitting on a nearby network on the same ISP.

Anyway, not much you can do about it except perhaps ask whatever MIS people to see if they got put on some blacklist or whatever.

I've obviously noticed the pull request despite it being in my spam folder.

Linus

Quoted 60 lines

- 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(-)
#3 lore raw
Quoted 4 lines · Linus Torvalds
Quoted 2 lines · David Sterba

please pull the following fixes for btrfs, thanks.

Quoted 8 lines

Hmm. I got two copies of this...

...and both were in my spam folder.

I don't see anything wrong with the message (spf and dkim both fine).so I assume it's something about suse.sz or suse.de that gmail doesn't like. Presumably some spammer sitting on a nearby network on the same ISP.

I don't know what could be wrong. Regular mails I send from mutt and the pull request with 'git send-email'. Today I sent the first pull request mail from mutt to see if there's a change from last time when you found the mail in spam. The mail delivery took longer than expected, I think more than half an hour which could be the gray listing period that I saw on vger in the past. So I sent it again with git send-mail, just to be sure. But if both end up in spam then it's probably something in the mail body, other mails seem to be delivered.

Quoted 4 lines

Anyway, not much you can do about it except perhaps ask whatever MIS people to see if they got put on some blacklist or whatever.

I've obviously noticed the pull request despite it being in my spam folder.

Good to know, thanks, I'll check if there's anything to do in my mail setup.

#4 lore raw
In reply to Linus Torvalds
Quoted 9 lines · Linus Torvalds

I don't see anything wrong with the message (spf and dkim both fine).so I assume it's something about suse.sz or suse.de that gmail doesn't like. Presumably some spammer sitting on a nearby network on the same ISP.

Anyway, not much you can do about it except perhaps ask whatever MIS people to see if they got put on some blacklist or whatever.

I've obviously noticed the pull request despite it being in my spam folder.

gmail seems to be going berserk lately, it keeps rejecting tons of mail from mailinglist for random reasons like too much traffic or a close IP apparently sent spam.