From: Chris Mason <chris.mason@fusionio.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Please hammer my for-linus branch
Date: Sat, 30 Jun 2012 21:22:59 -0400 [thread overview]
Message-ID: <20120701012259.GM17638@shiny> (raw)
Hi everyone,
I've got a nice set of fixes from Josef, Jan, Ilya and others in my
for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Some of the changes are fixes for the tree logging code, so I ran some
extra crash runs against them Friday night.
I ended up with a new crash in the tree log directory deletion replay
code, so I didn't send out the pull request to Linus.
It isn't clear yet if the new crash is because I was testing differently
or if it is a regression. I'm nailing it down this weekend, but please
give my for-linus a shot.
-chris
next reply other threads:[~2012-07-01 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 1:22 Chris Mason [this message]
2012-07-02 14:10 ` xfstests/224 lockup/slowdown (was: Please hammer my for-linus branch) David Sterba
2012-07-02 14:34 ` David Sterba
2012-07-02 16:10 ` David Sterba
2012-07-02 20:17 ` Please hammer my for-linus branch Chris Mason
2012-07-03 14:39 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2012-07-02 3:35 Daniel J Blueman
2012-07-02 4:20 ` Liu Bo
2012-07-10 12:18 ` Daniel J Blueman
2012-07-11 1:37 ` Liu Bo
2012-07-11 2:01 ` Daniel J Blueman
2012-07-02 13:34 ` Josef Bacik
2012-07-03 3:55 ` Daniel J Blueman
2012-07-04 3:37 ` Daniel J Blueman
2012-07-04 5:19 ` Liu Bo
2012-07-04 6:53 ` Daniel J Blueman
2012-07-05 13:26 ` Josef Bacik
2012-07-06 20:59 ` Josef Bacik
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=20120701012259.GM17638@shiny \
--to=chris.mason@fusionio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.