linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/1] Normalized path names on umounts (take 2)
Date: Mon,  5 Mar 2012 14:36:04 -0500	[thread overview]
Message-ID: <1330976165-19849-1-git-send-email-steved@redhat.com> (raw)

There is a second attempted at making paths in the
device names that have multiple slashes or no slash
at all unmount-able, without breaking any APIs.

Due to the way entries are written to both the /etc/mtab
and /proc/mounts, multiple slash have to be stripped and
leading slash have to be added (when they don't exist) 
on v4 mounts. With v3 mounts this normalization can 
not occur since those entries are always in the same format.

Finally, this normalization only needs to happen
when the mtab and /proc/mounts are not the same file.

Steve Dickson (1):
  umount.nfs: normalize path names during umounts.

 utils/mount/nfsumount.c |   64 +++++++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 62 insertions(+), 2 deletions(-)


             reply	other threads:[~2012-03-05 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 19:36 Steve Dickson [this message]
2012-03-05 19:36 ` [PATCH 1/1] umount.nfs: normalize path names during umounts Steve Dickson
2012-03-05 21:20   ` Malahal Naineni
2012-03-05 21:30     ` Malahal Naineni
2012-03-06  0:28       ` Steve Dickson
2012-03-06  0:27     ` Steve Dickson
2012-03-06  0:31       ` Myklebust, Trond
2012-03-06  0:53         ` Steve Dickson
2012-03-06  1:04           ` Myklebust, Trond
2012-03-06  1:35             ` Steve Dickson
2012-03-06  1:52               ` Jim Rees
2012-03-06  2:25                 ` Malahal Naineni
2012-03-06  2:38                   ` Steve Dickson
2012-03-05 19:37 ` [PATCH 0/1] Normalized path names on umounts (take 2) Chuck Lever
2012-03-05 19:44   ` Steve Dickson

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=1330976165-19849-1-git-send-email-steved@redhat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).