From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Can't unmount bad inode
Date: Wed, 19 Jan 2005 21:45:19 +0000 [thread overview]
Message-ID: <20050119214519.GG26051@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <E1CrNFz-0001JF-00@dorka.pomaz.szeredi.hu>
On Wed, Jan 19, 2005 at 10:20:51PM +0100, Miklos Szeredi wrote:
> Andrew,
>
> This patch fixes a problem when a inode which is the root of a mount
> becomes bad (make_bad_inode()). In this case follow_link will return
> -EIO, so the name resolution fails, and umount won't work. The
> solution is just to remove the follow_link method from bad_inode_ops.
> Any filesystem operation (other than unmount) will still fail, since
> every other method returns -EIO.
I'm not all that sure that we want to follow symlinks in the last
pathname component upon umount, actually...
next prev parent reply other threads:[~2005-01-19 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 21:20 Miklos Szeredi
2005-01-19 21:45 ` Al Viro [this message]
2005-01-19 21:58 ` Miklos Szeredi
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=20050119214519.GG26051@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
Powered by JetHome