From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 2/4] rbd: expand lock protection in rbd_add()
Date: Mon, 10 Sep 2012 15:05:46 -0700 [thread overview]
Message-ID: <504E643A.4050003@inktank.com> (raw)
In-Reply-To: <504A09AD.80905@inktank.com>
Looking closer, I don't think we need to protect this section at all.
The device isn't initialized yet, so nothing else can access the
rbd_dev->header. It'd be good to have a comment to that effect.
Josh
On 09/07/2012 07:50 AM, Alex Elder wrote:
> Expand the region of code in rbd_add() protected by the header
> semaphore to include the complete initialization sequence. It may
> not be strictly necessary, but it doesn't hurt. And with the
> upcoming changes to the order of steps here this offers easy
> protection.
>
> Signed-off-by: Alex Elder <elder@inktank.com>
> ---
> drivers/block/rbd.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 214c937..6af09f1 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -2553,6 +2553,8 @@ static ssize_t rbd_add(struct bus_type *bus,
> INIT_LIST_HEAD(&rbd_dev->snaps);
> init_rwsem(&rbd_dev->header_rwsem);
>
> + down_write(&rbd_dev->header_rwsem);
> +
> /* generate unique id: find highest unique id, add one */
> rbd_dev_id_get(rbd_dev);
>
> @@ -2598,18 +2600,17 @@ static ssize_t rbd_add(struct bus_type *bus,
> /* contact OSD, request size info about the object being mapped */
> rc = rbd_read_header(rbd_dev, &rbd_dev->header);
> if (rc)
> - goto err_out_bus;
> + goto err_out_unlock;
>
> - /* no need to lock here, as rbd_dev is not registered yet */
> rc = rbd_dev_snap_devs_update(rbd_dev);
> if (rc)
> - goto err_out_bus;
> + goto err_out_unlock;
>
> - down_write(&rbd_dev->header_rwsem);
> rc = rbd_header_set_snap(rbd_dev, snap_name);
> - up_write(&rbd_dev->header_rwsem);
> if (rc)
> - goto err_out_bus;
> + goto err_out_unlock;
> +
> + up_write(&rbd_dev->header_rwsem);
>
> /* Set up the blkdev mapping. */
>
> @@ -2630,6 +2631,8 @@ static ssize_t rbd_add(struct bus_type *bus,
>
> return count;
>
> +err_out_unlock:
> + up_write(&rbd_dev->header_rwsem);
> err_out_bus:
> /* this will also clean up rest of rbd_dev stuff */
>
> @@ -2649,6 +2652,7 @@ err_put_id:
> kfree(rbd_dev->pool_name);
> }
> rbd_dev_id_put(rbd_dev);
> + up_write(&rbd_dev->header_rwsem);
> err_nomem:
> kfree(rbd_dev);
> kfree(options);
>
next prev parent reply other threads:[~2012-09-10 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 14:47 [PATCH 0/4] rbd: locking, snapshot registration, snap_by_name() Alex Elder
2012-09-07 14:50 ` [PATCH 1/4] rbd: move locking out of rbd_header_set_snap() Alex Elder
2012-09-10 21:57 ` Josh Durgin
2012-09-07 14:50 ` [PATCH 2/4] rbd: expand lock protection in rbd_add() Alex Elder
2012-09-10 22:05 ` Josh Durgin [this message]
2012-09-11 13:52 ` Alex Elder
2012-09-11 14:33 ` Josh Durgin
2012-09-07 14:50 ` [PATCH 3/4] rbd: don't register snapshots in bus_add_dev() Alex Elder
2012-09-10 22:21 ` Josh Durgin
2012-09-07 14:50 ` [PATCH 4/4] rbd: use snaps list in rbd_snap_by_name() Alex Elder
2012-09-10 22:32 ` Josh Durgin
2012-09-11 14:05 ` 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=504E643A.4050003@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@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.