From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Mason <clm@fb.com>, btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Fix for btrfs/070 checksum error
Date: Wed, 22 Jul 2015 17:28:48 +0800 [thread overview]
Message-ID: <55AF6250.8070602@cn.fujitsu.com> (raw)
In-Reply-To: <559C9A75.60506@cn.fujitsu.com>
Hi Chris,
Is there anything wrong with it?
It has been 2 weeks, and it's still not in your for linus branch.
Is there anything wrong?
Thanks,
Qu
Qu Wenruo wrote on 2015/07/08 11:35 +0800:
> Hi Chris,
>
> Sorry for the late pull request, this one should be sent on Monday. :(
>
> This patchset is meant to fix an annoying bug triggered by btrfs/070 and
> some other concurrency scrub + IO load test.
>
> The bug itself is triggered by chance and took Zhao Lei quite a long
> time to trace and debug it.
>
> Although previous patchset sent to mail-list has some problem, it turned
> out that's rebasing typo, and can be fixed quite easy.
>
> We have spend a whole weekend running tests this time to ensure the
> patch is OK.
>
> The fix itself is small enough and only fixes a long standing problem.
> IMHO it is OK for the late fix merge window.
>
> So please merge the following branch:
> https://github.com/adam900710/linux.git for_chris_4.2_070_fix
>
> Thanks,
> Qu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-22 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 3:35 [GIT PULL] Fix for btrfs/070 checksum error Qu Wenruo
2015-07-22 9:28 ` Qu Wenruo [this message]
2015-07-22 11:58 ` Chris Mason
2015-07-23 20:21 ` Chris Mason
2015-07-24 0:29 ` Qu Wenruo
2015-07-24 1:57 ` Chris Mason
2015-07-24 2:50 ` Qu Wenruo
2015-07-28 7:10 ` Qu Wenruo
2015-07-29 8:21 ` Zhao Lei
2015-07-29 14:52 ` 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=55AF6250.8070602@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.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).