From: Daniel Phillips <phillips@google.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Lock recursion in rpc_pipefs+auth_gss...
Date: Thu, 19 Jan 2006 11:27:03 -0800 [thread overview]
Message-ID: <43CFE807.5080304@google.com> (raw)
Hi Trond,
You wrote:
> I believe I've finally figured out what is causing the Oopses that Vince
> and Vincent were seeing. It all boils down to a mutex being held after
> the inode is released due to a deadlock situation.
That in itself should not cause an oops. I would think there is a
reference-counting problem still lurking. I'm a little concerned that a
patch like this one may just make the oops a lot rarer without solving it.
Regards,
Daniel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2006-01-19 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 19:27 Daniel Phillips [this message]
2006-01-19 23:09 ` Re: Lock recursion in rpc_pipefs+auth_gss Trond Myklebust
2006-01-20 1:18 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2006-01-19 13:17 Trond Myklebust
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=43CFE807.5080304@google.com \
--to=phillips@google.com \
--cc=Trond.Myklebust@netapp.com \
--cc=nfs@lists.sourceforge.net \
/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.