From: viro@parcelfarce.linux.theplanet.co.uk
To: Andrew Morton <akpm@digeo.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] how to fix is_local_disk()?
Date: Mon, 5 May 2003 08:41:31 +0100 [thread overview]
Message-ID: <20030505074131.GA10374@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030504140537.50310417.akpm@digeo.com>
On Sun, May 04, 2003 at 02:05:37PM -0700, Andrew Morton wrote:
> About half of the s_umount grabbers perform that check. The others might be
> buggy. I'm not sure - it's all rather gunky in there and hard to tell what
> the rules are.
Very simple, actually - if you are holding an active reference, no checks
are needed. If you do not (as in this case) - you need to check that
filesystem is not in the middle of shutdown after getting ->s_umount.
prev parent reply other threads:[~2003-05-05 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 7:00 [RFC] how to fix is_local_disk()? Christoph Hellwig
2003-05-04 7:30 ` Andrew Morton
2003-05-04 7:53 ` Christoph Hellwig
2003-05-04 8:00 ` Andrew Morton
2003-05-04 17:10 ` Christoph Hellwig
2003-05-04 21:05 ` Andrew Morton
2003-05-05 7:41 ` viro [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=20030505074131.GA10374@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=akpm@digeo.com \
--cc=hch@lst.de \
--cc=linux-kernel@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 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.