All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guangliang Zhao <lucienchao@gmail.com>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] clean up read only mode
Date: Tue, 8 Oct 2013 11:40:54 +0800	[thread overview]
Message-ID: <20131008034054.GA2763@x230> (raw)
In-Reply-To: <1380604559-5331-1-git-send-email-josh.durgin@inktank.com>

On Mon, Sep 30, 2013 at 10:15:57PM -0700, Josh Durgin wrote:
> Running with lockdep showed that there were problems holding
> rbd_dev->lock while doing in the BLKROSET ioctl patch. Fix this, and
> clean up the initial read-only setting to occur during device
> initialization instead of every time the device is opened.
> 
> These are also available in the wip-rbd-ro branch of ceph-client.git.
> 
> Josh Durgin (2):
>   rbd: move calls that may sleep out of spin lock range
>   rbd: only set disk to read-only once

Both look good.

> 
>  drivers/block/rbd.c |   38 ++++++++++++++++++++++++--------------
>  1 files changed, 24 insertions(+), 14 deletions(-)
> 
> -- 
> 1.7.2.5
> 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Best regards,
Guangliang

  reply	other threads:[~2013-10-08  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  3:25 [PATCH v4] rbd: add ioctl for rbd Guangliang Zhao
2013-10-01  5:15 ` [PATCH 0/2] clean up read only mode Josh Durgin
2013-10-08  3:40   ` Guangliang Zhao [this message]
2013-10-01  5:15 ` [PATCH 1/2] rbd: move calls that may sleep out of spin lock range Josh Durgin
2013-10-01 21:17   ` Alex Elder
2013-10-01  5:15 ` [PATCH 2/2] rbd: only set disk to read-only once Josh Durgin
2013-10-01 21:21   ` Alex Elder

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=20131008034054.GA2763@x230 \
    --to=lucienchao@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@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.