From: Andreas Gruenbacher <agruen@suse.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ftp.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Tony Jones <tonyj@suse.de>,
Neil Brown <neilb@suse.de>, Christoph Hellwig <hch@lst.de>,
Greg Kroah-Hartman <gregkh@suse.de>, walt <wa1ter@myrealbox.com>
Subject: Re: [PATCH] Fix d_path for lazy unmounts
Date: Thu, 15 Feb 2007 05:19:38 -0800 [thread overview]
Message-ID: <200702150519.39299.agruen@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0702151349400.786@yvahk01.tjqt.qr>
On Thursday 15 February 2007 04:53, Jan Engelhardt wrote:
> What's the point in changing pipefs... you can *never*
> reach it *anyway*, even if it was a /-style path, since
> pipefs is a NOMNT filesystem.
The point is that we could then get rid of the special case for MS_NOUSER
filesystems like pipefs in __d_path(). (This special case caused the lazy
unmounted dir bug in the first place.) It is likely not really worth it,
though.
Andreas
prev parent reply other threads:[~2007-02-15 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 3:23 [PATCH] Fix d_path for lazy unmounts Andreas Gruenbacher
2007-02-05 0:15 ` Neil Brown
2007-02-15 2:43 ` Andreas Gruenbacher
2007-02-05 8:32 ` Andreas Gruenbacher
2007-02-05 18:37 ` [PATCH]Add memory barrier before clear bit in unlock_buffer() Mingming Cao
2007-02-14 8:19 ` [PATCH] Fix d_path for lazy unmounts Andreas Gruenbacher
2007-02-14 8:29 ` Olaf Hering
2007-02-14 8:42 ` Andreas Gruenbacher
2007-02-14 15:37 ` Linus Torvalds
2007-02-14 19:39 ` Andreas Gruenbacher
2007-02-14 22:57 ` Andreas Gruenbacher
2007-02-15 3:13 ` Andreas Gruenbacher
2007-02-17 13:30 ` Andreas Gruenbacher
2007-02-15 12:53 ` Jan Engelhardt
2007-02-15 13:19 ` Andreas Gruenbacher [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=200702150519.39299.agruen@suse.de \
--to=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=hch@lst.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tonyj@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
--cc=wa1ter@myrealbox.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.