From: Chris Mason <clm@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs for rc5
Date: Fri, 12 Sep 2014 12:35:28 -0400 [thread overview]
Message-ID: <541320D0.4060603@fb.com> (raw)
Hi Linus,
My for-linus branch has some fixes for the next rc:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Filipe is doing a careful pass through fsync problems, and these are the
fixes so far. I'll have one more for rc6 that we're still testing.
My big commit is fixing up some inode hash races that Al Viro found
(thanks Al).
Filipe Manana (3) commits (+75/-21):
Btrfs: fix corruption after write/fsync failure + fsync + log recovery (+9/-3)
Btrfs: fix fsync data loss after a ranged fsync (+64/-17)
Btrfs: fix crash while doing a ranged fsync (+2/-1)
Chris Mason (2) commits (+113/-70):
Btrfs: use insert_inode_locked4 for inode creation (+109/-67)
Btrfs: fix autodefrag with compression (+4/-3)
Dan Carpenter (1) commits (+15/-10):
Btrfs: kfree()ing ERR_PTRs
Total: (6) commits (+203/-101)
fs/btrfs/file.c | 2 +-
fs/btrfs/inode.c | 191 +++++++++++++++++++++++++++++++++-------------------
fs/btrfs/ioctl.c | 32 +++++----
fs/btrfs/tree-log.c | 77 ++++++++++++++++-----
fs/btrfs/tree-log.h | 2 +
5 files changed, 203 insertions(+), 101 deletions(-)
reply other threads:[~2014-09-12 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=541320D0.4060603@fb.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