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 updates for 4.20-rc4
Date: Wed, 28 Nov 2018 13:28:05 +0100 [thread overview]
Message-ID: <cover.1543407525.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes. Some of them are being hit during
testing so we'd like to get them merged, otherwise there are usual
stability fixes for stable trees. Thanks.
----------------------------------------------------------------
The following changes since commit d6fd0ae25c6495674dc5a41a8d16bc8e0073276d:
Btrfs: fix missing delayed iputs on unmount (2018-11-07 20:17:45 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.20-rc4-tag
for you to fetch changes up to 42a657f57628402c73237547f0134e083e2f6764:
btrfs: relocation: set trans to be NULL after ending transaction (2018-11-23 13:47:46 +0100)
----------------------------------------------------------------
Filipe Manana (3):
Btrfs: fix rare chances for data loss when doing a fast fsync
Btrfs: ensure path name is null terminated at btrfs_control_ioctl
Btrfs: fix race between enabling quotas and subvolume creation
Nikolay Borisov (1):
btrfs: Always try all copies when reading extent buffers
Pan Bian (1):
btrfs: relocation: set trans to be NULL after ending transaction
Robbie Ko (1):
Btrfs: send, fix infinite loop due to directory rename dependencies
fs/btrfs/disk-io.c | 11 +----------
fs/btrfs/file.c | 24 ++++++++++++++++++++++++
fs/btrfs/qgroup.c | 3 ++-
fs/btrfs/relocation.c | 1 +
fs/btrfs/send.c | 11 ++++++++---
fs/btrfs/super.c | 1 +
6 files changed, 37 insertions(+), 14 deletions(-)
next reply other threads:[~2018-11-28 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 12:28 David Sterba [this message]
2018-11-28 16:45 ` [GIT PULL] Btrfs updates for 4.20-rc4 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.1543407525.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).