Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	clm@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.1-rc5
Date: Thu, 11 Apr 2019 19:35:13 +0200	[thread overview]
Message-ID: <cover.1555003647.git.dsterba@suse.com> (raw)

Hi,

please pull the following updates that have some user-visible effects:

- fix parsing of compression algorithm when set as a inode property,
  this could end up with eg. 'zst' or 'zli' in the value

- don't allow trim on a filesystem with unreplayed log, this could cause
  data loss if there are pending updates to the block groups that would
  not be subject to trim after replay

Thanks.

----------------------------------------------------------------
The following changes since commit 0ccc3876e4b2a1559a4dbe3126dda4459d38a83b:

  Btrfs: fix assertion failure on fsync with NO_HOLES enabled (2019-03-20 19:53:39 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.1-rc4-tag

for you to fetch changes up to 272e5326c7837697882ce3162029ba893059b616:

  btrfs: prop: fix vanished compression property after failed set (2019-04-04 17:57:53 +0200)

----------------------------------------------------------------
Anand Jain (2):
      btrfs: prop: fix zstd compression parameter validation
      btrfs: prop: fix vanished compression property after failed set

Filipe Manana (1):
      Btrfs: do not allow trimming when a fs is mounted with the nologreplay option

 fs/btrfs/ioctl.c | 10 ++++++++++
 fs/btrfs/props.c |  8 ++++----
 2 files changed, 14 insertions(+), 4 deletions(-)

             reply	other threads:[~2019-04-11 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 17:35 David Sterba [this message]
2019-04-11 21:45 ` [GIT PULL] Btrfs fixes for 5.1-rc5 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.1555003647.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.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