From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: lockd: couldn't create RPC handle for (host)
Date: Sun, 18 Dec 2005 17:24:24 -0500 [thread overview]
Message-ID: <1134944665.11596.9.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20051218200052.GA21665@tau.solarneutrino.net>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Sun, 2005-12-18 at 15:00 -0500, Ryan Richter wrote:
> On Sun, Dec 18, 2005 at 02:31:07PM -0500, Trond Myklebust wrote:
> > On Sun, 2005-12-18 at 13:01 -0500, Ryan Richter wrote:
> > > Code: 48 39 78 18 75 1c 8b 86 8c 00 00 00 a8 01 74 12 83 c8 02 89
> > > RIP <ffffffff801dbd9e>{nlmclnt_mark_reclaim+62} RSP <ffff81007dfade70>
> > > CR2: 0000000000000018
> >
> > Looks like the global lock list is corrupted. Could you cat the contents
> > of /proc/locks?
>
> $ cat /proc/locks
> 1: POSIX ADVISORY WRITE 1657 00:0e:1771273 0 EOF
> 2: FLOCK ADVISORY WRITE 1486 00:0e:1770759 0 EOF
> 3: FLOCK ADVISORY WRITE 1478 00:0e:1770399 0 EOF
OK. I think this client patch ought to fix the Oopses. It should apply
to a 2.6.14 kernel as well as 2.6.15-rc5.
Cheers,
Trond
[-- Attachment #2: linux-2.6.15-49-fix_nlm_recovery_oops.dif --]
[-- Type: text/plain, Size: 1088 bytes --]
NLM: Fix Oops in nlmclnt_mark_reclaim()
When mixing -olock and -onolock mounts on the same client, we have to
check that fl->fl_u.nfs_fl.owner is set before dereferencing it.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
---
fs/lockd/clntlock.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/fs/lockd/clntlock.c b/fs/lockd/clntlock.c
index 006bb9e..3eaf6e7 100644
--- a/fs/lockd/clntlock.c
+++ b/fs/lockd/clntlock.c
@@ -157,6 +157,8 @@ void nlmclnt_mark_reclaim(struct nlm_hos
inode = fl->fl_file->f_dentry->d_inode;
if (inode->i_sb->s_magic != NFS_SUPER_MAGIC)
continue;
+ if (fl->fl_u.nfs_fl.owner == NULL)
+ continue;
if (fl->fl_u.nfs_fl.owner->host != host)
continue;
if (!(fl->fl_u.nfs_fl.flags & NFS_LCK_GRANTED))
@@ -226,6 +228,8 @@ restart:
inode = fl->fl_file->f_dentry->d_inode;
if (inode->i_sb->s_magic != NFS_SUPER_MAGIC)
continue;
+ if (fl->fl_u.nfs_fl.owner == NULL)
+ continue;
if (fl->fl_u.nfs_fl.owner->host != host)
continue;
if (!(fl->fl_u.nfs_fl.flags & NFS_LCK_RECLAIM))
next prev parent reply other threads:[~2005-12-18 22:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 20:55 Ryan Richter
2005-12-16 23:49 ` Trond Myklebust
2005-12-16 23:58 ` Ryan Richter
2005-12-17 5:32 ` Trond Myklebust
2005-12-17 5:59 ` Ryan Richter
2005-12-17 6:43 ` Trond Myklebust
2005-12-17 7:02 ` Ryan Richter
2005-12-17 19:28 ` Trond Myklebust
2005-12-17 19:45 ` Ryan Richter
2005-12-18 8:33 ` Trond Myklebust
2005-12-18 18:01 ` Ryan Richter
2005-12-18 19:31 ` Trond Myklebust
2005-12-18 20:00 ` Ryan Richter
2005-12-18 22:24 ` Trond Myklebust [this message]
2005-12-18 22:44 ` Ryan Richter
2006-01-03 19:01 ` Ryan Richter
2006-01-18 0:02 ` Ryan Richter
2006-02-27 20:37 ` Ryan Richter
2005-12-19 18:49 ` [NFS] " Dan Stromberg
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=1134944665.11596.9.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=ryan@tau.solarneutrino.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®