All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donald Douwsma <donaldd@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] refactor xfs_mountfs for clarity & stack savings
Date: Mon, 01 Oct 2007 17:49:30 +1000	[thread overview]
Message-ID: <4700A68A.8070609@sgi.com> (raw)
In-Reply-To: <46D48BDE.5000903@sandeen.net>

Eric Sandeen wrote:
> Refactoring xfs_mountfs() to call sub-functions for logical
> chunks can help save a bit of stack, and can make it easier to
> read this long function.

Finally got around to reviewing this one, sorry for the delay.

I think we've lost something in the refactoring.

> Index: linux-2.6-xfs/fs/xfs/xfs_mount.c
...
> -	/*
> -	 * XFS uses the uuid from the superblock as the unique
> -	 * identifier for fsid.  We can not use the uuid from the volume
> -	 * since a single partition filesystem is identical to a single
> -	 * partition volume/filesystem.
> -	 */
> -	if ((mfsi_flags & XFS_MFSI_SECOND) == 0 &&
> -	    (mp->m_flags & XFS_MOUNT_NOUUID) == 0) {
> -		if (xfs_uuid_mount(mp)) {
> -			error = XFS_ERROR(EINVAL);
> -			goto error1;
> -		}
> -		uuid_mounted=1;

The patch removes uuid_mounted=1, but doesn't put it back in anywhere.
I think we need that bit for error handling :)

Don

  parent reply	other threads:[~2007-10-01  7:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28  1:29 [PATCH] refactor xfs_mountfs for clarity & stack savings Eric Sandeen
2007-08-28 19:52 ` Christoph Hellwig
2007-08-28 20:24   ` Eric Sandeen
2007-08-28 20:55   ` [PATCH V2] " Eric Sandeen
2007-09-18 14:36     ` Christoph Hellwig
2007-09-29  9:48     ` Christoph Hellwig
2007-10-01  7:49     ` Donald Douwsma [this message]
2007-10-01 12:39       ` Eric Sandeen

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=4700A68A.8070609@sgi.com \
    --to=donaldd@sgi.com \
    --cc=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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.