All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] mkfs.gfs2: Follow symlinks before checking device contents
Date: Wed, 20 Jun 2012 19:27:20 +0200	[thread overview]
Message-ID: <4FE207F8.3070604@redhat.com> (raw)
In-Reply-To: <5a30bad4-2f62-4ac7-b356-3a2e3a298878@zmail12.collab.prod.int.phx2.redhat.com>

Hi,

On 6/20/2012 6:15 PM, Bob Peterson wrote:
> ----- Original Message -----
> | +	absname = canonicalize_file_name(sdp->device_name);
> 
> Hi Andy,
> 
> Thanks for the patch. I just wanted to point out that in the past we've
> used realpath rather than canonicalize_file_name. For example, see this patch
> we did a long time ago to gfs2_tool:
> 
> http://git.fedorahosted.org/git/?p=cluster.git;a=commitdiff;h=e70898cfa09939a7100a057433fff3a4ad666bdd
> 
> It would be nice if our use was consistent. I'm not sure if there's an
> advantage of one over the other. If canonicalize_file_name is now preferred
> upstream over realpath, we should probably replace all occurrences of that.
> 
> On the other hand, if realpath is now preferred upstream, we should adjust
> this patch to use it instead. AFAIK, they are the same, and I don't have a
> personal preference; whatever is most favoured by the upstream community. :)
> 
> Otherwise, the patch looks good.

I don?t remember what other mkfs.* tools do, but if I would prefer to
see something like:

# ./mkfs.gfs2 -p lock_nolock /dev/vg/test
WARNING: /dev/vg/test appears to be a symlink to /dev/real/device
This will destroy any data on /dev/real/device
It appears to contain: RANDOM_FS_OF_DOOM (blocksize......)

Fabio






  reply	other threads:[~2012-06-20 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 15:47 [Cluster-devel] [PATCH] mkfs.gfs2: Follow symlinks before checking device contents Andrew Price
2012-06-20 16:15 ` Bob Peterson
2012-06-20 17:27   ` Fabio M. Di Nitto [this message]
2012-06-20 17:42   ` Andrew Price
2012-06-28  9:16 ` Steven Whitehouse
2012-06-28  9:58   ` Andrew Price
2012-06-28 10:01     ` Steven Whitehouse
2012-06-28 17:52       ` Andrew Price
2012-07-04 11:02         ` Andrew Price
2012-07-04 11:15           ` Steven Whitehouse

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=4FE207F8.3070604@redhat.com \
    --to=fdinitto@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 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.