From: Alex Elder <elder@ieee.org>
To: Ilya Dryomov <ilya.dryomov@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] __remove_osd() vs lingering requests
Date: Wed, 05 Nov 2014 11:49:54 -0600 [thread overview]
Message-ID: <545A6342.4000404@ieee.org> (raw)
In-Reply-To: <1415208804-10163-1-git-send-email-idryomov@redhat.com>
On 11/05/2014 11:33 AM, Ilya Dryomov wrote:
> Hello,
>
> These are fixes for the problem I found while trying to reproduce
> recently reopened http://tracker.ceph.com/issues/5429. I'm pretty sure
> this is what was reported in http://tracker.ceph.com/issues/8568 too.
> The exact BUG_ON() it points to is no longer there, but I checked with
> an older kernel and the reproducer I have for this triggered it.
>
> Thanks,
>
> Ilya
All three of these look good to me. The interactions with
these lists has always been a bit too tricky; you've done a
lot to make sense of them.
And I'm sure there are other BUG_ON() (or rbd_assert()) calls
that can be tamed--either removed, changed to warnings, or
changed to simply return errors where possible.
Reviewed-by: Alex Elder <elder@linaro.org>
>
>
> Ilya Dryomov (3):
> libceph: unlink from o_linger_requests when clearing r_osd
> libceph: clear r_req_lru_item in __unregister_linger_request()
> libceph: change from BUG to WARN for __remove_osd() asserts
>
> net/ceph/osd_client.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2014-11-05 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 17:33 [PATCH 0/3] __remove_osd() vs lingering requests Ilya Dryomov
2014-11-05 17:33 ` [PATCH 1/3] libceph: unlink from o_linger_requests when clearing r_osd Ilya Dryomov
2014-11-05 17:33 ` [PATCH 2/3] libceph: clear r_req_lru_item in __unregister_linger_request() Ilya Dryomov
2014-11-05 17:33 ` [PATCH 3/3] libceph: change from BUG to WARN for __remove_osd() asserts Ilya Dryomov
2014-11-05 17:49 ` Alex Elder [this message]
2014-11-05 18:42 ` [PATCH 0/3] __remove_osd() vs lingering requests Ilya Dryomov
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=545A6342.4000404@ieee.org \
--to=elder@ieee.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ilya.dryomov@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.