[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1555003647.git.dsterba@suse.com>
Date: Thu, 11 Apr 2019 19:35:13 +0200
From: David Sterba <dsterba@...e.com>
To: torvalds@...ux-foundation.org
Cc: David Sterba <dsterba@...e.com>, clm@...com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.1-rc5
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(-)
Powered by blists - more mailing lists