From: Jens Axboe <axboe@kernel.dk>
To: "xan.peng" <xanpeng@gmail.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>,
daniel.gollub@gmail.com
Subject: Re: A possible patch for a dangling pointer issue of librbd engine
Date: Mon, 19 May 2014 09:37:41 -0600 [thread overview]
Message-ID: <537A2545.80104@kernel.dk> (raw)
In-Reply-To: <CA+8ZFnjK+68M1aSp4pFx=orD4fhM0D+Qi1QOjpQsDBwQvOhVSA@mail.gmail.com>
On 05/18/2014 07:58 PM, xan.peng wrote:
> I'm interested in the librbd engine, and I possibly found a bug which
> you can see from the following patch.
>
> And you can see more information at https://github.com/axboe/fio/pull/10.
> (BTW, are github pull requests the correct way to submit patches to fio?)
Sure, you can do that, but email me+list about them separately as I
might not see them on github. So I'm not going to pull your branch,
since you have two patches on top of the interesting one, where the 2nd
just reverts the other one. I'm apply this one separately.
--
Jens Axboe
next prev parent reply other threads:[~2014-05-19 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 1:58 A possible patch for a dangling pointer issue of librbd engine xan.peng
2014-05-19 15:37 ` Jens Axboe [this message]
2014-05-19 16:38 ` xan.peng
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=537A2545.80104@kernel.dk \
--to=axboe@kernel.dk \
--cc=daniel.gollub@gmail.com \
--cc=fio@vger.kernel.org \
--cc=xanpeng@gmail.com \
/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.