From: Christoph Hellwig <hch@caldera.de>
To: Andries.Brouwer@cwi.nl
Cc: alan@lxorguk.ukuu.org.uk, hch@caldera.de, torvalds@transmeta.com,
viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: [semiPATCH] another vxfs fix
Date: Fri, 3 Aug 2001 09:56:40 +0200 [thread overview]
Message-ID: <20010803095640.A9328@caldera.de> (raw)
In-Reply-To: <200108030043.AAA103538@vlet.cwi.nl>
In-Reply-To: <200108030043.AAA103538@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Fri, Aug 03, 2001 at 12:43:48AM +0000
On Fri, Aug 03, 2001 at 12:43:48AM +0000, Andries.Brouwer@cwi.nl wrote:
>
> With the brelse() fix, a failed vxfs mount is OK.
> But after a successful vxfs mount the umount still yields
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day
> (And today's [yesterday's] patch by Christoph makes no difference.)
>
> The reason is that the routine vxfs_fake_inode() does
> new_inode(), but this inode is never returned.
> I fixed this but am not sure against which base source
> the patch should be described.
> A minimal version would be to change the six [1] calls of
> vxfs_put_inode()
> in vxfs_super.c into calls of
> iput()
>
> (In my source I turned vxfs_fake_inode() into vxfs_get_fake_inode()
> and added vxfs_put_fake_inode() that just does iput().)
Sounds fine - just submit me any version and I'll rebase it against
the latest Linus and Alan trees.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
parent reply other threads:[~2001-08-03 7:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200108030043.AAA103538@vlet.cwi.nl>]
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=20010803095640.A9328@caldera.de \
--to=hch@caldera.de \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.