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, part 2
Date: Tue, 30 Oct 2018 14:23:52 +0100 [thread overview]
Message-ID: <cover.1540904580.git.dsterba@suse.com> (raw)
Hi,
this part contains a few minor updates and fixes that were under testing
or arrived shortly after the merge window freeze, mostly stable material.
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit d9352794dad9f28535439d85a815978878c141ab:
btrfs: switch return_bigger to bool in find_ref_head (2018-10-15 17:23:41 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.20-part2-tag
for you to fetch changes up to 9084cb6a24bf5838a665af92ded1af8363f9e563:
Btrfs: fix use-after-free when dumping free space (2018-10-22 20:31:22 +0200)
----------------------------------------------------------------
Filipe Manana (5):
Btrfs: fix null pointer dereference on compressed write path error
Btrfs: fix assertion on fsync of regular file when using no-holes feature
Btrfs: fix deadlock when writing out free space caches
Btrfs: fix use-after-free during inode eviction
Btrfs: fix use-after-free when dumping free space
Josef Bacik (8):
MAINTAINERS: update my email address for btrfs
btrfs: reset max_extent_size properly
btrfs: set max_extent_size properly
btrfs: don't use ctl->free_space for max_extent_size
btrfs: only free reserved extent if we didn't insert it
btrfs: fix insert_reserved error handling
btrfs: don't run delayed_iputs in commit
btrfs: move the dio_sem higher up the callchain
Lu Fengqi (1):
btrfs: delayed-ref: extract find_first_ref_head from find_ref_head
MAINTAINERS | 2 +-
fs/btrfs/ctree.c | 17 +++++++++++++++
fs/btrfs/delayed-ref.c | 50 ++++++++++++++++++++++++---------------------
fs/btrfs/extent-tree.c | 37 +++++++++++++++------------------
fs/btrfs/file.c | 12 +++++++++++
fs/btrfs/free-space-cache.c | 32 ++++++++++++++++++++---------
fs/btrfs/inode.c | 15 ++++++++++++--
fs/btrfs/transaction.c | 9 --------
fs/btrfs/tree-log.c | 5 ++---
9 files changed, 111 insertions(+), 68 deletions(-)
next reply other threads:[~2018-10-30 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 13:23 David Sterba [this message]
2018-10-30 15:28 ` [GIT PULL] Btrfs updates for 4.20, part 2 Linus Torvalds
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.1540904580.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).