linux-kernel - Re: [GIT PULL] Btrfs fixes for 5.18-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAADWXX-XPrfiD0TLGwMuzmGfs9pZ+HiTo1v9cs-mxb6x0OXpZw@mail.gmail.com>
Date:   Tue, 5 Apr 2022 08:58:35 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     David Sterba <dsterba@...e.com>
Cc:     linux-btrfs <linux-btrfs@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Btrfs fixes for 5.18-rc2

On Tue, Apr 5, 2022 at 6:28 AM David Sterba <dsterba@...e.com> wrote:
>
> 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

>
> - 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(-)