From: "wlacey" <wlacey@goldenhindresearch.com>
To: linux-mips@linux-mips.org
Subject: RPC: exit -512 [ERESTARTSYS]
Date: Thu, 25 Mar 2004 22:22:41 [thread overview]
Message-ID: <20040325222241.3445.qmail@server212.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
I'm bringing up a 2.4.18 version of the kernel on a tx4925 processor, using a NFS'ed root filesystem when the actual mount request RPC call fails w/-512
About line 662 in function __rpc_execute(), in file net/sunrpc/sched.c
if (task->tk_client->cl_intr && signalled())) {
printk("RPC: got signal\n");
task->tk_flags |= RPC_TASK_KILLED;
rpc_exit(task, -ERESTARTSYS);
rpc_wake_up_task(task);
}
}
}
if (task->tk_exit) {
task->tk_exit(task);
/* If tk_action is non-null, the user wants us to restart */
if (task->tk_action) {
..
..
The problems is that rpc_exit() NULLS task->tk_action and I can't see how the task/RPC request gets re-generated.
Is anybody familiar w/this area of code? Why is the RPC call apparently not being re-generated?
Any help???
Thanks,
Warrick Lacey
[-- Attachment #2: Type: text/html, Size: 999 bytes --]
reply other threads:[~2004-03-25 22:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040325222241.3445.qmail@server212.com \
--to=wlacey@goldenhindresearch.com \
--cc=linux-mips@linux-mips.org \
/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