From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Rob Dege" <rcd@amherst.com>
Cc: "nfs" <nfs@lists.sourceforge.net>
Subject: Re: Kernel paging dump on 2.4.18
Date: 23 Apr 2002 11:03:25 +0200 [thread overview]
Message-ID: <shsy9fedbxe.fsf@charged.uio.no> (raw)
In-Reply-To: <GKEPJBFFKGJCJDOINKHJMELHCFAA.rcd@amherst.com>
>>>>> " " == Rob Dege <rcd@amherst.com> writes:
> I'm running RedHat 7.2 w/2.4.18 as a dedicated file server
> prmailily for Linux & alpha machines. I've been getting kernel
> paging faults, and don't know what's causing it. The odd thing
> is that the kernel error only affects NFS. Everything else is
> stable, and usable. here's the dump from /var/log/messages:
That looks like a bug I fixed a long time ago in 2.2.x. Does the
following patch help?
Cheers,
Trond
diff -u --recursive --new-file linux-2.4.18/fs/lockd/svc4proc.c linux-2.4.18-fix_lock/fs/lockd/svc4proc.c
--- linux-2.4.18/fs/lockd/svc4proc.c Mon Oct 1 22:45:47 2001
+++ linux-2.4.18-fix_lock/fs/lockd/svc4proc.c Tue Apr 23 11:00:59 2002
@@ -254,6 +254,7 @@
dprintk("lockd: TEST_MSG called\n");
+ memset(&res, 0, sizeof(res));
if ((stat = nlm4svc_proc_test(rqstp, argp, &res)) == 0)
stat = nlm4svc_callback(rqstp, NLMPROC_TEST_RES, &res);
return stat;
diff -u --recursive --new-file linux-2.4.18/fs/lockd/svcproc.c linux-2.4.18-fix_lock/fs/lockd/svcproc.c
--- linux-2.4.18/fs/lockd/svcproc.c Thu Oct 11 16:52:18 2001
+++ linux-2.4.18-fix_lock/fs/lockd/svcproc.c Tue Apr 23 11:01:10 2002
@@ -282,6 +282,7 @@
dprintk("lockd: TEST_MSG called\n");
+ memset(&res, 0, sizeof(res));
if ((stat = nlmsvc_proc_test(rqstp, argp, &res)) == 0)
stat = nlmsvc_callback(rqstp, NLMPROC_TEST_RES, &res);
return stat;
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-04-23 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 18:19 Kernel paging dump on 2.4.18 Rob Dege
2002-04-23 9:03 ` Trond Myklebust [this message]
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=shsy9fedbxe.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=rcd@amherst.com \
/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