From: Alex Elder <elder@inktank.com>
To: Dan van der Ster <dan@vanderster.com>
Cc: Sage Weil <sage@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] rbd: don't zero-fill non-image object requests
Date: Wed, 27 Mar 2013 15:10:04 -0500 [thread overview]
Message-ID: <5153521C.7000900@inktank.com> (raw)
In-Reply-To: <CABZ+qqkVnj3qrKyhOmOX=vAn67Xjq1oKUFcPyCruT591qthYYQ@mail.gmail.com>
On 03/27/2013 11:26 AM, Dan van der Ster wrote:
> On Wed, Mar 27, 2013 at 5:10 PM, Sage Weil <sage@inktank.com> wrote:
>> Does this only affect the current -rc or is this problem older than that?
The bug I found should affect only the new request code,
which if I am not mistaken got to sent to Linus during this
cycle (3.9-rcX).
> The BUG I reported that triggered this was on 3.8.4.
OK, now I'm trying to reproduce the problem with 3.8.4 and
I'm not seeing any crashes...
Hmm. I'll look a little more closely.
-Alex
> --
> Dan
>
prev parent reply other threads:[~2013-03-27 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 14:28 [PATCH] rbd: don't zero-fill non-image object requests Alex Elder
2013-03-27 16:10 ` Sage Weil
2013-03-27 16:26 ` Dan van der Ster
2013-03-27 20:10 ` Alex Elder [this message]
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=5153521C.7000900@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dan@vanderster.com \
--cc=sage@inktank.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.