public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
	reiserfs-dev@namesys.com, adilger@turbolabs.com
Subject: Re: [reiserfs-dev] [PATCH] UUID & volume labels support for reiserfs
Date: Wed, 09 Jan 2002 12:14:28 -0500	[thread overview]
Message-ID: <179160000.1010596468@tiny> (raw)
In-Reply-To: <20020109194430.A2058@namesys.com>
In-Reply-To: <20020109155504.A4551@namesys.com> <52160000.1010591279@tiny> <20020109185826.A1680@namesys.com> <100150000.1010592449@tiny> <20020109192526.A1732@namesys.com> <145590000.1010594312@tiny> <20020109194430.A2058@namesys.com>



On Wednesday, January 09, 2002 07:44:30 PM +0300 Oleg Drokin
<green@namesys.com> wrote:

> Does filling something with zeroes counts as "using the field"? ;)

We must be reading different versions of generate_random_uuid ;-)

> 
>> The point is that we should never add something to the kernel until our
>> utils package understands it.  Yes, this is a simple case, but if we want
> In fact, current reiserfsprogs understands these fields (look into the
> the struct super_block definition in reiserfsprogs). It just cannot
> change content of the fields.

/* Structure of super block on disk */
struct reiserfs_super_block
{
/*  0 */    struct reiserfs_super_block_v1 s_v1;
/* 76 */    char sb_mnt_version[16];
/* 92 */    char sb_mkfs_version[16];
/*108 */    char sb_fsck_version[16];
/*124 */    char sb_unused[204-16-16-16-SB_SIZE_V1] ;
/* zero filled by mkreiserfs */ };

Show me the part where it knows what a uuid is.  It should at least be able
to show the uuid set by the kernel.

Please don't take this the wrong way, this is a good (and simple) patch
that adds a cool feature.  We just need to do a better job of having the
utils support the features before sending the patch it.  It does a better
job of proving we've tested the feature and that kernel patch fully meets
our needs.

-chris


  reply	other threads:[~2002-01-09 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 12:55 [PATCH] UUID & volume labels support for reiserfs Oleg Drokin
2002-01-09 15:47 ` [reiserfs-dev] " Chris Mason
2002-01-09 15:58   ` Oleg Drokin
2002-01-09 16:07     ` Chris Mason
2002-01-09 16:25       ` Oleg Drokin
2002-01-09 16:38         ` Chris Mason
2002-01-09 16:44           ` Oleg Drokin
2002-01-09 17:14             ` Chris Mason [this message]
2002-01-11  9:23               ` Oleg Drokin

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=179160000.1010596468@tiny \
    --to=mason@suse.com \
    --cc=adilger@turbolabs.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=reiserfs-dev@namesys.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