All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Just <sam.just@inktank.com>
To: Sage Weil <sweil@redhat.com>
Cc: Ding Dinghua <dingdinghua85@gmail.com>,
	Gregory Farnum <greg@gregs42.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Confused about SnapMapper::get_prefix
Date: Mon, 9 Feb 2015 09:23:09 -0800	[thread overview]
Message-ID: <CA+4uBUa2adqgNyYHQbyi-ft1C87bEZXt_04FYcEakUGY3xAKeA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1502080707030.27042@cobra.newdream.net>

I think that's right.  Do you want to create a pull request against hammer?
-Sam

On Sun, Feb 8, 2015 at 7:07 AM, Sage Weil <sweil@redhat.com> wrote:
> This looks right to me.  Sam?
>
> sage
>
>
> On Sun, 8 Feb 2015, Ding Dinghua wrote:
>
>> Ping..
>>
>> I think so, snap_id is defined and used as uint64_t in ceph, but here
>> static_cast may introduce bug, since two snap_id may get the same
>> prefix, then same key in snap_mapper.
>>
>> diff --git a/src/osd/SnapMapper.cc b/src/osd/SnapMapper.cc
>> index 315e2e2..27cc2b7 100644
>> --- a/src/osd/SnapMapper.cc
>> +++ b/src/osd/SnapMapper.cc
>> @@ -72,8 +72,7 @@ string SnapMapper::get_prefix(snapid_
>> t snap)
>>    char buf[100];
>>    int len = snprintf(
>>      buf, sizeof(buf),
>> -    "%.*X_", (int)(sizeof(snap)*2),
>> -    static_cast<unsigned>(snap));
>> +    "%.*llX_", (int)(sizeof(snap)*2), snap);
>>
>> 2015-02-04 12:02 GMT+08:00 Ding Dinghua <dingdinghua85@gmail.com>:
>> > I think so, snap_id is defined and used as uint64_t in ceph, but here
>> > static_cast may introduce bug, since two snap_id may get the same
>> > prefix, then same key in snap_mapper.
>> >
>> > diff --git a/src/osd/SnapMapper.cc b/src/osd/SnapMapper.cc
>> > index 315e2e2..27cc2b7 100644
>> > --- a/src/osd/SnapMapper.cc
>> > +++ b/src/osd/SnapMapper.cc
>> > @@ -72,8 +72,7 @@ string SnapMapper::get_prefix(snapid_
>> > t snap)
>> >    char buf[100];
>> >    int len = snprintf(
>> >      buf, sizeof(buf),
>> > -    "%.*X_", (int)(sizeof(snap)*2),
>> > -    static_cast<unsigned>(snap));
>> > +    "%.*llX_", (int)(sizeof(snap)*2), snap);
>> >
>> > 2015-02-04 1:25 GMT+08:00 Samuel Just <sam.just@inktank.com>:
>> >> Should probably be cast to long unsigned with lX conversion specifier?
>> >> -Sam
>> >>
>> >> On Tue, Feb 3, 2015 at 9:21 AM, Samuel Just <sam.just@inktank.com> wrote:
>> >>> It looks like snapid_t is a uint64_t, but snprintf expects an unsigned there.
>> >>> -Sam
>> >>>
>> >>> On Tue, Feb 3, 2015 at 9:15 AM, Gregory Farnum <greg@gregs42.com> wrote:
>> >>>> On Tue, Feb 3, 2015 at 4:12 AM, Ding Dinghua <dingdinghua85@gmail.com> wrote:
>> >>>>> Hi all:
>> >>>>>       I don't understand why SnapMapper::get_prefix   static_cast snap
>> >>>>> to unsigned:
>> >>>>>
>> >>>>> string SnapMapper::get_prefix(snapid_t snap)
>> >>>>> {
>> >>>>>   char buf[100];
>> >>>>>   int len = snprintf(
>> >>>>>     buf, sizeof(buf),
>> >>>>>     "%.*X_", (int)(sizeof(snap)*2),
>> >>>>>     static_cast<unsigned>(snap));
>> >>>>>   return MAPPING_PREFIX + string(buf, len);
>> >>>>> }
>> >>>>>
>> >>>>> Will this limit snapshot count in pool to 2^32 -1 ?
>> >>>>>
>> >>>>> Could anyone clarify ? Thanks
>> >>>>
>> >>>> I think the code base is a little confused about whether snaps should
>> >>>> be 32 or 64 bits in various places. :( That said, the size of unsigned
>> >>>> can vary across architectures, so this should probably be sized more
>> >>>> explicitly as whatever it's supposed to be on the disk...
>> >
>> >
>> >
>> > --
>> > Ding Dinghua
>>
>>
>>
>> --
>> Ding Dinghua
>> --
>> 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
>>
>>

      reply	other threads:[~2015-02-09 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 12:12 Confused about SnapMapper::get_prefix Ding Dinghua
2015-02-03 17:15 ` Gregory Farnum
2015-02-03 17:21   ` Samuel Just
2015-02-03 17:25     ` Samuel Just
2015-02-04  4:02       ` Ding Dinghua
2015-02-08 14:17         ` Ding Dinghua
2015-02-08 15:07           ` Sage Weil
2015-02-09 17:23             ` Samuel Just [this message]

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=CA+4uBUa2adqgNyYHQbyi-ft1C87bEZXt_04FYcEakUGY3xAKeA@mail.gmail.com \
    --to=sam.just@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dingdinghua85@gmail.com \
    --cc=greg@gregs42.com \
    --cc=sjust@redhat.com \
    --cc=sweil@redhat.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.