linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
	Sidong Yang <realwakka@gmail.com>
Subject: Re: Btrfs progs release 5.11.1
Date: Mon, 26 Apr 2021 16:45:10 +0100	[thread overview]
Message-ID: <CAL3q7H6tRX9C9RYCCaE+PxBcVwht168Kb-m+YVSy2abctuQhWg@mail.gmail.com> (raw)
In-Reply-To: <20210324192858.19011-1-dsterba@suse.com>

On Wed, Mar 24, 2021 at 7:35 PM David Sterba <dsterba@suse.com> wrote:
>
> Hi,
>
> btrfs-progs version 5.11.1 have been released. This is a bugfix release.
>
> Changelog:
>
>   * properly format checksums when a mismatch is reported
>   * check: fix false alert on tree block crossing 64K page boundary
>   * convert:
>     * refuse to convert filesystem with 'needs_recovery'
>     * update documentation to require fsck before conversion
>   * balance convert: fix raid56 warning when converting other profiles
>   * fi resize: improved summary
>   * other
>     * build: fix checks and autoconf defines
>     * fix symlink paths for CI support scripts
>     * updated tests
>
> Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
> Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
>
> Shortlog:
>
> David Sterba (10):
>       btrfs-progs: ci: fix symlink paths of helper scripts
>       btrfs-progs: tests: extend mkfs/001 to look for warnings after mkfs
>       btrfs-progs: mkfs: enumerate all supported checksum algorithms in help text
>       btrfs-progs: convert: refuse to convert filesystem with 'needs_recovery' set
>       btrfs-progs: tests: add crafted image to test needs_recovery
>       btrfs-progs: docs: change wording about required fsck
>       btrfs-progs: balance: fix raid56 warning for other profiles
>       btrfs-progs: tests: verify that ext4 supports extra_isize
>       btrfs-progs: update CHANGES for 5.11.1
>       Btrfs progs v5.11.1
>
> Dāvis Mosāns (1):
>       btrfs-progs: fix checksum output for "checksum verify failed"
>
> Heiko Becker (1):
>       btrfs-progs: build: Use PKG_CONFIG instead of pkg-config
>
> Jaak Ristioja (1):
>       btrfs-progs: check: fix typos in code comment and 1 typo in warning
>
> Pierre Labastie (3):
>       btrfs-progs: tests: fix quoting of sudo helper in misc/046-seed-multi-mount
>       btrfs-progs: build: fix the test for EXT4_EPOCH_MASK
>       btrfs-progs: build: do not use AC_DEFINE twice for a FIEMAP define
>
> Qu Wenruo (1):
>       btrfs-progs: fix false alert on tree block crossing 64K page boundary
>
> Sidong Yang (1):
>       btrfs-progs: fi resize: make output more readable

Btw, due to the new output, this path now makes btrfs/177 from fstests fail:

btrfs/177 5s ... - output mismatch (see
/home/fdmanana/git/hub/xfstests/results//btrfs/177.out.bad)
    --- tests/btrfs/177.out 2020-06-10 19:29:03.822519250 +0100
    +++ /home/fdmanana/git/hub/xfstests/results//btrfs/177.out.bad
2021-04-26 16:25:37.708323523 +0100
    @@ -1,4 +1,4 @@
     QA output created by 177
    -Resize 'SCRATCH_MNT' of '3221225472'
    +Resize device id 1 (SCRATCH_DEV) from 1.00GiB to 0.00B
     Text file busy
    -Resize 'SCRATCH_MNT' of '1073741824'
    +Resize device id 1 (SCRATCH_DEV) from 3.00GiB to 0.00B
    ...
    (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/177.out
/home/fdmanana/git/hub/xfstests/results//btrfs/177.out.bad'  to see
the entire diff)

Thanks.

>


-- 
Filipe David Manana,

“Whether you think you can, or you think you can't — you're right.”

  reply	other threads:[~2021-04-26 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 19:28 Btrfs progs release 5.11.1 David Sterba
2021-04-26 15:45 ` Filipe Manana [this message]
2021-05-10 19:25   ` David Sterba

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=CAL3q7H6tRX9C9RYCCaE+PxBcVwht168Kb-m+YVSy2abctuQhWg@mail.gmail.com \
    --to=fdmanana@gmail.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=realwakka@gmail.com \
    /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).