From: Greg Banks <gnb@sgi.com>
To: James Pearson <james-p@moving-picture.com>
Cc: autofs@linux.kernel.org, nfs@lists.sourceforge.net,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [NFS] Re: Busy inodes after unmount followed by Oops
Date: Sat, 22 May 2004 23:04:57 +1000 [thread overview]
Message-ID: <20040522130457.GB15564@sgi.com> (raw)
In-Reply-To: <40AE3532.8EBA0D7B@moving-picture.com>
On Fri, May 21, 2004 at 05:58:26PM +0100, James Pearson wrote:
> Not quite sure what you mean by this - I had tried Greg's patch
> (http://marc.theaimsgroup.com/?l=linux-nfs&m=107604754127538&w=2)
> previously - but it made no difference in my case. The kernel I'm using
> now has both Greg's patch and Ian's recent autofs4 patch.
The error message and subsequent oops are both generic symptoms and
could come from any kind of race with umount which causes a dentry
or inode reference count leak, not just the particular one in NFS
which I fixed. There could well be another NFS bug like this, or
one in autofs. Ian's patch may have fixed it, hidden it, or just
stopped tickling it.
The only way to tell for sure is to modify the code that generates
the message to BUG() instead and use a kernel debugger to figure out
what has gone wrong. Note that using a debugger at oops time is
already too late.
James, are you able to reproduce this at will?
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
next prev parent reply other threads:[~2004-05-22 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 11:06 Busy inodes after unmount followed by Oops James Pearson
2004-01-09 19:13 ` [NFS] " Ian Kent
2004-05-21 15:44 ` James Pearson
2004-05-21 16:44 ` Trond Myklebust
2004-05-21 16:44 ` Trond Myklebust
2004-05-21 16:58 ` [NFS] " James Pearson
2004-05-22 13:04 ` Greg Banks [this message]
2004-05-22 15:15 ` raven
2004-05-22 15:24 ` raven
2004-05-24 15:51 ` James Pearson
2004-05-22 3:41 ` raven
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=20040522130457.GB15564@sgi.com \
--to=gnb@sgi.com \
--cc=autofs@linux.kernel.org \
--cc=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.