From: Andreas Dilger <adilger@clusterfs.com>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, sct@redhat.com
Subject: Re: [PATCH] ext3: return FSID for statvfs
Date: Wed, 7 Dec 2005 13:01:09 -0700 [thread overview]
Message-ID: <20051207200109.GG14509@schatzie.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.58.0512071512170.21616@sbz-30.cs.Helsinki.FI>
On Dec 07, 2005 15:13 +0200, Pekka J Enberg wrote:
> On Wed, 7 Dec 2005, Andreas Dilger wrote:
> > The bug mentions some reasons why this patch is sub-optimal - namely that
> > the beginning of the UUID has common fields in it. It may make more sense
> > to e.g. XOR the first 2 * u32 with the last 2 * u32 to reduce the chance
> > of an FSID collision.
>
> This patch changes ext3_statfs() to return a FSID based on 64 bit XOR of the
> 128 bit filesystem UUID as suggested by Andreas Dilger. This patch is partial
> fix for Bugzilla Bug <http://bugzilla.kernel.org/show_bug.cgi?id=136>.
That seems at least slightly better, as it involves all the bits.
Question - what is rule for "Signed-off-by:"? I'm hesitant to add that if
I haven't actually compiled+tested a fix, as I've seen too many instances
of "obvious fix contains bug" to believe visual inspection is enough. If
"Signed-off-by:" simply indicates "Yes, this person approves of the change
in principle" then that's OK by me. Andrew, do you use the "CC" tag for
that?
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
>
> super.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> Index: 2.6/fs/ext3/super.c
> ===================================================================
> --- 2.6.orig/fs/ext3/super.c
> +++ 2.6/fs/ext3/super.c
> @@ -2294,6 +2294,7 @@ static int ext3_statfs (struct super_blo
> struct ext3_super_block *es = EXT3_SB(sb)->s_es;
> unsigned long overhead;
> int i;
> + u64 fsid;
>
> if (test_opt (sb, MINIX_DF))
> overhead = 0;
> @@ -2340,6 +2341,10 @@ static int ext3_statfs (struct super_blo
> buf->f_files = le32_to_cpu(es->s_inodes_count);
> buf->f_ffree = ext3_count_free_inodes (sb);
> buf->f_namelen = EXT3_NAME_LEN;
> + fsid = le64_to_cpup((void *)es->s_uuid) ^
> + le64_to_cpup((void *)es->s_uuid + sizeof(u64));
> + buf->f_fsid.val[0] = fsid & 0xFFFFFFFFUL;
> + buf->f_fsid.val[1] = (fsid >> 32) & 0xFFFFFFFFUL;
> return 0;
> }
>
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2005-12-07 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 20:23 Pekka Enberg
2005-12-07 12:40 ` Andreas Dilger
2005-12-07 13:13 ` Pekka J Enberg
2005-12-07 20:01 ` Andreas Dilger [this message]
2005-12-08 7:28 ` Pekka J Enberg
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=20051207200109.GG14509@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.Helsinki.FI \
--cc=sct@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®