From: Sebastien Ponce <sebastien.ponce@cern.ch>
To: Joaquim Rocha <joaquim.rocha@cern.ch>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Possible bug when getting batched xattrs
Date: Fri, 17 Oct 2014 13:01:18 +0200 [thread overview]
Message-ID: <1413543678.1245.17.camel@sebmain.cern.ch> (raw)
In-Reply-To: <5440E131.2020501@cern.ch>
I can confirm that head of master has the same behavior.
On top, having had a look at the osd code (name ly ReplicatedPG.cc
around line 4756 in master), it seems to be intended : we are in a for
loop going through the operations and executing them and the code says :
if (result < 0)
break;
So we exit the loop on the first error and do not execute the remaining
ops.
Sebastien
On Fri, 2014-10-17 at 11:28 +0200, Joaquim Rocha wrote:
> Hi,
>
> I need to get a list of xattrs from one object (so I'm batching them in
> one ObjectReadOperation) but I don't know in advance if all of those
> xattrs exist.
>
> I was expecting to figure out the ones that don't exist from the return
> code of each getxattr call but I have however noticed that as soon one
> nonexistent xattr is processed, its return code gets correctly set to
> -ENODATA but the remaining xattrs are never checked. And what is worse,
> the remaining getxattr op's return codes get assigned to 0.
>
> I am attaching a small test case I've quickly written that proves the
> case. (I am using Ceph 0.80.5)
>
> Could you confirm that this is not the intended behavior (that all read
> op's calls should be processed)?
>
>
> Thank you in advance,
>
> --
> Joaquim Rocha
> http://www.joaquimrocha.com
next prev parent reply other threads:[~2014-10-17 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 9:28 Possible bug when getting batched xattrs Joaquim Rocha
2014-10-17 11:01 ` Sebastien Ponce [this message]
2014-10-17 14:02 ` Sage Weil
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=1413543678.1245.17.camel@sebmain.cern.ch \
--to=sebastien.ponce@cern.ch \
--cc=ceph-devel@vger.kernel.org \
--cc=joaquim.rocha@cern.ch \
/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