public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Pekka 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 05:40:43 -0700	[thread overview]
Message-ID: <20051207124043.GD14509@schatzie.adilger.int> (raw)
In-Reply-To: <1133900600.3279.7.camel@localhost>

On Dec 06, 2005  22:23 +0200, Pekka Enberg wrote:
> This patch changes ext3_statfs() to return a FSID based on least significant
> 64-bits of the 128-bit filesystem UUID. This patch is a partial fix for
> Bugzilla Bug <http://bugzilla.kernel.org/show_bug.cgi?id=136>.

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.

Also, there is a tiny memory of a security issue with exposing the FSID
to applications (something to do with NFS and guessing filehandles or
similar).  I have no idea if that is even relevant any longer, but
thought I'd mention it.

> @@ -2340,6 +2340,8 @@ 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;
> +	buf->f_fsid.val[0] = le32_to_cpup((void *)es->s_uuid);
> +	buf->f_fsid.val[1] = le32_to_cpup((void *)es->s_uuid + sizeof(u32));
>  	return 0;
>  }
>  

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


  reply	other threads:[~2005-12-07 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 20:23 [PATCH] ext3: return FSID for statvfs Pekka Enberg
2005-12-07 12:40 ` Andreas Dilger [this message]
2005-12-07 13:13   ` Pekka J Enberg
2005-12-07 20:01     ` Andreas Dilger
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=20051207124043.GD14509@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