From: Tim Hockin <thockin@hockin.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: lazy-umount cwd and ..
Date: Wed, 5 May 2004 23:58:56 -0700 [thread overview]
Message-ID: <20040506065856.GA21004@hockin.org> (raw)
In-Reply-To: <20040506064617.GQ17014@parcelfarce.linux.theplanet.co.uk>
On Thu, May 06, 2004 at 07:46:17AM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Wed, May 05, 2004 at 09:44:33PM -0700, Tim Hockin wrote:
> > Should I bother to polish this patch off and send it, or is it just not
> > something we want to care about?
>
> No. This is simply wrong - one of the situations when you want lazy-umount
> is getting a stuck filesystem (e.g. NFS mounted hard) and wanting to get
> it out of the way, so that stuff it's mounted on could be unmounted clean.
>
> So we definitely don't want to keep anything pinned down.
I'll buy that. I guess it's not worth dreaming up something else to make
that be less surprising to apps with cwd in a lazy umounted mount.
Cheers.
prev parent reply other threads:[~2004-05-06 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 4:44 lazy-umount cwd and Tim Hockin
2004-05-06 6:46 ` viro
2004-05-06 6:58 ` Tim Hockin [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=20040506065856.GA21004@hockin.org \
--to=thockin@hockin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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