From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Nicholas L. Nigay" <nnigay@cboss.ru>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: oops 2.4.19-rc1 process lockd ( part 3 : no vmware )]
Date: 01 Jul 2002 14:36:02 +0200 [thread overview]
Message-ID: <shs4rfjsk0d.fsf@charged.uio.no> (raw)
In-Reply-To: <3D203E6B.4010300@cboss.ru>
>>>>> " " == Nicholas L Nigay <nnigay@cboss.ru> writes:
>>> EIP; c02ac415 <xdr_encode_netobj+15/4c> <=====
>>> eax; 300c9800 Before first symbol ebx; cb4e6058
>>> <_end+b13cd48/1047fcf0> ecx; cb4e6058 <_end+b13cd48/1047fcf0>
>>> edx; cc99be64 <_end+c5f2b54/1047fcf0> esi; cc99be6c
>>> <_end+c5f2b5c/1047fcf0> edi; c0186fc8
>>> <nlm4clt_encode_testres+0/30> ebp; cc400900
>>> <_end+c0575f0/1047fcf0> esp; cd319d94 <_end+cf70a84/1047fcf0>
> Trace; c0186fc8 <nlm4clt_encode_testres+0/30> Trace; c0186719
> <nlm4_encode_testres+89/1f0> Trace; c0186fc8
> <nlm4clt_encode_testres+0/30> Trace; c0186fdc
> <nlm4clt_encode_testres+14/30> Trace; c02a47fc
> <call_encode+d8/104> Trace; c02a79ac <__rpc_execute+a8/2bc>
> Trace; c02a4496 <rpc_call_setup+3e/70> Trace; c02a7c17
> <rpc_execute+57/70> Trace; c02a4431 <rpc_call_async+7d/a4>
> Trace; c018168a <nlmsvc_async_call+82/98> Trace; c0187a0c
> <nlm4svc_callback_exit+0/54> Trace; c01879e7
> <nlm4svc_callback+73/98> Trace; c0187a0c
> <nlm4svc_callback_exit+0/54> Trace; c01874e8
> <nlm4svc_proc_test_msg+48/54> Trace; c026a316
> <inet_sendmsg+3a/40> Trace; c0237065 <sock_sendmsg+69/88>
> Trace; c0186417 <nlm4_decode_oh+f/14> Trace; c018647c
> <nlm4_decode_lock+4c/130> Trace; c018649a
> <nlm4_decode_lock+6a/130> Trace; c018691a
> <nlm4svc_decode_testargs+4e/54> Trace; c02a9d81
> <svc_process+219/4d8> Trace; c018278e <lockd+19a/254> Trace;
> c0107028 <kernel_thread+28/38>
Patch appended...
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;
prev parent reply other threads:[~2002-07-01 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 11:35 [Fwd: oops 2.4.19-rc1 process lockd ( part 3 : no vmware )] Nicholas L. Nigay
2002-07-01 12:36 ` 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=shs4rfjsk0d.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nnigay@cboss.ru \
/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