From: Ric Wheeler <ric@emc.com>
To: Jeff Mahoney <jeffm@suse.com>,
Vladimir Saveliev <Vladimir.Saveliev@sun.com>
Cc: Edward Shishkin <edward.shishkin@gmail.com>,
ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH 2/2] reiserfs: Add mount counting
Date: Wed, 05 Dec 2007 07:22:11 -0500 [thread overview]
Message-ID: <475697F3.8050209@emc.com> (raw)
In-Reply-To: <47548A90.3060805@suse.com>
Jeff Mahoney wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Edward Shishkin wrote:
>> On 12/4/07, Jeff Mahoney <jeffm@suse.com> wrote:
>> Edward Shishkin wrote:
>>>>> On 12/3/07, Jeff Mahoney <jeffm@suse.com> wrote:
>>>>> Edward Shishkin wrote:
>>>>>>>> Hi Jeff.
>>>>>>>>
>>>>>>>> Personally, I don't object.
>>>>>>>> What does official reservation mean?
>>>>>>>> I can send a request to Hans, but I guess
>>>>>>>> we'll receive his "yes" or "no" with substantial delay..
>>>>> I just mean that those 12 bytes in the superblock are guaranteed not to
>>>>> be used for something else. Given the pace of reiserfs development, I
>>>>> don't expect this to be a problem as there are 76 more of them. :)
>>>>>
>>>>>> Well, I promise to not use them for something else ;)
>> Great. That's the assurance I was looking for. :)
>>
>>>>>> It seems we need something like reiserfsprogs-3.6.20?
>> I actually posted a patch against reiserfsprogs-3.6.20 that reserves the
>> same fields. It also implements the use of those fields. I have an
>> updated version that treats timestamps in the future as suspect and
>> forces a check. I'll post the update later today.
>>
>>> Sorry, I am a bit confused..
>>> The latest git version of reiserfsprogs is 3.6.19;
>>> The latest website version is also 3.6.19.
>>> At the same time I can google and see that some distros
>>> use reiserfsprogs-3.6.20.
>>> Suse 10.3 uses "reiserfs utility package" 3.6.19-92
>>> Also I remember that Vladimir worked on some version
>>> of reiserfsprogs not so long ago.
>>> Any ideas about really latest version?
>
> I think Vladimir must have released what he was working on as 3.6.20.
> That's the latest version I downloaded from ftp.namesys.com.
>
> It reorganizes the code into a saner structure as well as cleans up the
> code quite a bit. It also adds the > 8 TB support that I ended up
> grafting onto 3.6.19 for our release.
>
> - -Jeff
>
We have also been working with & testing a draft of Vladimir's updated
code (not sure how different it is from what you took in).
Vladimir, did Jeff's drop include all of the changes or part of what you
did with us?
We can certainly update or refresh our copy for the next phase of qa,
thanks!
ric
next prev parent reply other threads:[~2007-12-05 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:42 [PATCH 2/2] reiserfs: Add mount counting Jeff Mahoney
2007-12-03 19:46 ` Jeff Mahoney
2007-12-03 20:36 ` Edward Shishkin
2007-12-03 20:40 ` Jeff Mahoney
2007-12-03 20:51 ` Edward Shishkin
2007-12-03 21:32 ` Jeff Mahoney
2007-12-03 22:56 ` Edward Shishkin
2007-12-03 23:00 ` Jeff Mahoney
2007-12-05 12:22 ` Ric Wheeler [this message]
2007-12-05 13:01 ` Vladimir Saveliev
2007-12-05 15:32 ` Jeff Mahoney
2007-12-05 15:39 ` Ric Wheeler
2007-12-05 15:52 ` Jeff Mahoney
2007-12-05 17:53 ` Vladimir Saveliev
2007-12-05 18:18 ` Ric Wheeler
2008-01-24 19:52 ` Jeff Mahoney
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=475697F3.8050209@emc.com \
--to=ric@emc.com \
--cc=Vladimir.Saveliev@sun.com \
--cc=edward.shishkin@gmail.com \
--cc=jeffm@suse.com \
--cc=reiserfs-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).