public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com
Subject: Btrfs progs release 4.16.1
Date: Tue, 24 Apr 2018 13:58:57 +0200	[thread overview]
Message-ID: <20180424115857.25174-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 4.16.1 have been released.  This is a bugfix release.

Changes:

  * remove obsolete tools: btrfs-debug-tree, btrfs-zero-log, btrfs-show-super,
    btrfs-calc-size
  * sb-mod: new debugging tool to edit superblock items
  * mkfs: detect if thin-provisioned device does not have enough space
  * check: don't try to verify checksums on metadata dump images
  * build: fail documentation build if xmlto is not found
  * build: fix build of btrfs.static

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:

Baruch Siach (1):
      btrfs-progs: build btrfs.static needs libbtrfsutil to build

David Sterba (5):
      btrfs-progs: sb-mod: add preliminary support for non-u64 types
      btrfs-progs: sb-mod: add csum_type
      btrfs-progs: sb-mod: add compat bit to the recognized fields
      btrfs-progs: reorder extent buffer members for better packing
      btrfs-progs: update CHANGES for v4.16.1

Gu Jinxiang (4):
      btrfs-progs: send-utils: remove unused functions path_cat and path_cat3
      btrfs-progs: Let function find_device to be consistent with kernel
      btrfs-progs: Remove duplicate value-get for data_extents_scrubbed
      btrfs-progs: Do not add extra slash if given path end with it

Misono Tomohiro (1):
      btrfs-progs: configure: check if xmlto exists at configure time

Nikolay Borisov (4):
      btrfs-progs: Remove btrfs-debug-tree command
      btrfs-progs: Remove deprecated btrfs-zero-log standalone tool
      btrfs-progs: Remove deprecated btrfs-show-super
      btrfs-progs: Remove deprecated btrfs-calc-size tool

Qu Wenruo (9):
      btrfs-progs: check: Skip data csum verification for metadata dump
      btrfs-progs: tests/fsck: Add test case to check if btrfs check can skip data csum verfication for metadata dump
      btrfs-progs: extent_io: Fix NULL pointer dereference in free_extent_buffer_final()
      btrfs-progs: extent_io: Init eb->lru to avoid NULL pointer dereference
      btrfs-progs: extent_io: Refactor alloc_extent_buffer() to follow kernel parameters
      btrfs-progs: Unify btrfs_leaf_free_space() parameter with kernel
      btrfs-progs: print-tree: Remove btrfs_root parameter
      btrfs-progs: Rename OPEN_CTREE_FS_PARTIAL to OPEN_CTREE_TEMPORARY_SUPER
      btrfs-progs: Use more loose open ctree flags for dump-tree and restore

Su Yue (1):
      btrfs-progs: mkfs: return nozero value on thin provisioned device

             reply	other threads:[~2018-04-24 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 11:58 David Sterba [this message]
2018-04-25  6:31 ` Btrfs progs release 4.16.1 Duncan
2018-04-25 11:02   ` David Sterba
2018-04-25 11:22     ` Austin S. Hemmelgarn
2018-04-25 11:29       ` Christoph Anton Mitterer
2018-04-25 11:49         ` Austin S. Hemmelgarn
2018-04-25 17:56     ` Duncan

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=20180424115857.25174-1-dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.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