From: Karel Zak <kzak@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: util-linux@vger.kernel.org,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
Franck Bui <fbui@suse.com>
Subject: Re: [util-linux PATCH] umount: never 'stat' the path when "-c" is given.
Date: Tue, 6 Jun 2017 11:43:58 +0200 [thread overview]
Message-ID: <20170606094358.it2vnzppmabsrone@ws.net.home> (raw)
In-Reply-To: <8760gbduzp.fsf@notabene.neil.brown.name>
On Mon, Jun 05, 2017 at 12:32:58PM +1000, NeilBrown wrote:
> So, this patch treats "-c" much like "-l" and "-f" when
> deciding whether it is safe to 'stat' the path.
Ah, definitely good idea. Applied, thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2017-06-06 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 2:32 [util-linux PATCH] umount: never 'stat' the path when "-c" is given NeilBrown
2017-06-05 2:38 ` [nfs-utils PATCH] umount.nfs: assume path name is canonical NeilBrown
2017-06-13 12:40 ` Steve Dickson
2017-06-06 9:43 ` Karel Zak [this message]
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=20170606094358.it2vnzppmabsrone@ws.net.home \
--to=kzak@redhat.com \
--cc=fbui@suse.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=util-linux@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).