From: Chris Mason <clm@fb.com>
To: <torvalds@linux-foundation.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs fix
Date: Fri, 6 Feb 2015 15:16:05 -0500 [thread overview]
Message-ID: <20150206201558.GA16241@ret.masoncoding.com> (raw)
Hi Linus,
Forrest Liu tracked down a missing blk_finish_plug in the btrfs logging
code. This isn't a new bug, and it's hard to hit. But, it's safe enough
for inclusion now, and in my for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
I missed the cc: stable, but I'll send it along to them as well.
Forrest Liu (1) commits (+1/-0):
Btrfs: add missing blk_finish_plug in btrfs_sync_log()
Total: (1) commits (+1/-0)
fs/btrfs/tree-log.c | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2015-02-06 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 20:16 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-08 21:32 [GIT PULL] Btrfs fix Chris Mason
2015-01-30 16:48 Chris Mason
2011-10-03 18:25 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=20150206201558.GA16241@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