CEPH filesystem development
 help / color / mirror / Atom feed
From: Alex Elder <elder@ieee.org>
To: Ilya Dryomov <ilya.dryomov@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] rbd: don't treat CEPH_OSD_OP_DELETE as extent op
Date: Mon, 24 Nov 2014 06:23:02 -0600	[thread overview]
Message-ID: <54732326.7050301@ieee.org> (raw)
In-Reply-To: <1416823190-10246-1-git-send-email-idryomov@redhat.com>

On 11/24/2014 03:59 AM, Ilya Dryomov wrote:
> CEPH_OSD_OP_DELETE is not an extent op, stop treating it as such.  This
> sneaked in with discard patches - it's one of the three osd ops (the
> other two are CEPH_OSD_OP_TRUNCATE and CEPH_OSD_OP_ZERO) that discard
> is implemented with.
> 
> Signed-off-by: Ilya Dryomov <idryomov@redhat.com>

Is the CEPH_OSD_OP_DELETE used in ceph_zero_partial_object()
an extent op?  If it is not, you should get rid of the BUG_ON()
in osd_req_op_extent_init() that allows CEPH_OSD_OP_DELETE.

And if that's the case it looks like that function or
ceph_osdc_new_request() handle CEPH_OSD_OP_DELETE
properly--so it's not treated as an extent op.

And:  osd_req_encode_op() encodes a CEPH_OSD_OP_DELETE
as an extent op as well.

If it *can* be an extent op (but just not as used by RBD)
then it warrants a comment here that explains why it is
not being initialized as an extent op.

					-Alex

> ---
>  drivers/block/rbd.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 27b71a0b72d0..1df0802bf6cb 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -2370,8 +2370,12 @@ static void rbd_img_obj_request_fill(struct rbd_obj_request *obj_request,
>  		opcode = CEPH_OSD_OP_READ;
>  	}
>  
> -	osd_req_op_extent_init(osd_request, num_ops, opcode, offset, length,
> -				0, 0);
> +	if (opcode == CEPH_OSD_OP_DELETE)
> +		osd_req_op_init(osd_request, num_ops, opcode);
> +	else
> +		osd_req_op_extent_init(osd_request, num_ops, opcode,
> +				       offset, length, 0, 0);
> +
>  	if (obj_request->type == OBJ_REQUEST_BIO)
>  		osd_req_op_extent_osd_data_bio(osd_request, num_ops,
>  					obj_request->bio_list, length);
> 


  reply	other threads:[~2014-11-24 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24  9:59 [PATCH] rbd: don't treat CEPH_OSD_OP_DELETE as extent op Ilya Dryomov
2014-11-24 12:23 ` Alex Elder [this message]
2014-11-24 13:30   ` Ilya Dryomov
2014-11-24 17:46     ` 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=54732326.7050301@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox