From: Chris Mason <clm@fb.com>
To: <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [GIT PULL] Btrfs fixes
Date: Fri, 1 May 2015 10:08:05 -0400 [thread overview]
Message-ID: <20150501140750.GA16744@ret.masoncoding.com> (raw)
Hi Linus,
I have a few more btrfs fixes in my for-linus-4.1 branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.1
These range from corners Filipe found in the new free space cache
writeback to a grab bag of fixes from the list.
Omar Sandoval (4) commits (+38/-19):
btrfs: unlock i_mutex after attempting to delete subvolume during send (+2/-1)
btrfs: check io_ctl_prepare_pages return in __btrfs_write_out_cache (+6/-4)
btrfs: fix race on ENOMEM in alloc_extent_buffer (+2/-1)
btrfs: handle ENOMEM in btrfs_alloc_tree_block (+28/-13)
Forrest Liu (2) commits (+37/-29):
Btrfs: btrfs_release_extent_buffer_page didn't free pages of dummy extent (+26/-25)
Btrfs: fix find_free_dev_extent() malfunction in case device tree has hole (+11/-4)
Filipe Manana (2) commits (+28/-18):
Btrfs: fix race between start dirty bg cache writeout and bg deletion (+27/-17)
Btrfs: fix deadlock when starting writeback of bg caches (+1/-1)
Yang Dongsheng (1) commits (+14/-9):
Btrfs: fill ->last_trans for delayed inode in btrfs_fill_inode.
Chris Mason (1) commits (+1/-2):
Btrfs: don't check for delalloc_bytes in cache_save_setup
Total: (10) commits (+118/-77)
fs/btrfs/delayed-inode.c | 2 +
fs/btrfs/extent-tree.c | 90 ++++++++++++++++++++++++++++-----------------
fs/btrfs/extent_io.c | 54 ++++++++++++++-------------
fs/btrfs/free-space-cache.c | 10 +++--
fs/btrfs/inode.c | 21 ++++++-----
fs/btrfs/ioctl.c | 3 +-
fs/btrfs/volumes.c | 15 ++++++--
7 files changed, 118 insertions(+), 77 deletions(-)
next reply other threads:[~2015-05-01 14:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 14:08 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-13 22:01 [GIT PULL] Btrfs fixes Chris Mason
2015-11-05 11:20 fdmanana
2015-11-05 14:59 ` Chris Mason
2015-05-15 19:11 Chris Mason
2015-04-26 13:18 Chris Mason
2015-03-20 16:55 Chris Mason
2015-01-23 18:49 Chris Mason
2015-01-08 18:28 Chris Mason
2014-11-01 16:05 Chris Mason
2014-09-19 19:47 Chris Mason
2013-03-17 12:34 Chris Mason
2013-02-07 0:13 Chris Mason
2013-02-07 0:09 Chris Mason
2013-01-23 0:48 Chris Mason
2013-01-23 1:28 ` Liu Bo
2013-01-23 1:40 ` Chris Mason
2013-01-24 21:52 ` Chris Mason
2013-01-25 3:13 ` Linus Torvalds
2012-10-26 14:19 Chris Mason
2012-05-06 13:35 Chris Mason
2012-04-28 12:27 Chris Mason
2012-01-27 16:34 Chris Mason
2012-01-27 16:31 Chris Mason
2011-12-23 17:24 Chris Mason
2011-12-16 17:53 Chris Mason
2011-12-16 18:20 ` Chris Mason
2011-12-16 18:29 ` nobody
2011-12-08 19:24 Chris Mason
2011-11-22 1:30 Chris Mason
2011-11-11 21:40 Chris Mason
2011-09-19 23:57 Chris Mason
2011-09-20 16:19 ` Sage Weil
2011-07-08 18:55 [GIT PULL] btrfs fixes Chris Mason
2011-07-11 11:31 ` Tarkan Erimer
2010-04-12 20:00 [GIT PULL] Btrfs fixes Chris Mason
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=20150501140750.GA16744@ret.masoncoding.com \
--to=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).