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.2-rc6
Date: Tue, 18 Jun 2019 18:52:07 +0200 [thread overview]
Message-ID: <cover.1560875945.git.dsterba@suse.com> (raw)
Hi,
please pull the following btrfs fixes:
- regression where properties stored as xattrs are not properly
persisted
- a small readahead fix (the fstests testcase for that fix hangs on
unpatched kernel, so we'd like get it merged to ease future testing)
- fix a race during block group creation and deletion
Thanks.
----------------------------------------------------------------
The following changes since commit 8103d10b71610aa65a65d6611cd3ad3f3bd7beeb:
btrfs: Always trim all unallocated space in btrfs_trim_free_extents (2019-06-07 14:52:05 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.2-rc5-tag
for you to fetch changes up to 3763771cf60236caaf7ccc79cea244c63d7c49a0:
Btrfs: fix failure to persist compression property xattr deletion on fsync (2019-06-17 16:37:17 +0200)
----------------------------------------------------------------
Filipe Manana (2):
Btrfs: fix race between block group removal and block group allocation
Btrfs: fix failure to persist compression property xattr deletion on fsync
Naohiro Aota (1):
btrfs: start readahead also in seed devices
fs/btrfs/extent-tree.c | 24 +++++++++++++-----------
fs/btrfs/ioctl.c | 2 --
fs/btrfs/reada.c | 5 +++++
fs/btrfs/xattr.c | 6 +++---
4 files changed, 21 insertions(+), 16 deletions(-)
next reply other threads:[~2019-06-18 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 16:52 David Sterba [this message]
2019-06-18 18:25 ` [GIT PULL] Btrfs fixes for 5.2-rc6 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.1560875945.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;
as well as URLs for NNTP newsgroup(s).