From: Andrew Morton <andrewm@uow.edu.au>
To: "Brian O'Keefe" <okeefe@spinnakernet.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@cse.unsw.edu.au>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: NFS client deadlock on SMP machines
Date: Wed, 10 Jan 2001 19:27:30 +1100 [thread overview]
Message-ID: <3A5C1CF2.170E0A04@uow.edu.au> (raw)
In-Reply-To: <3A5B42BF.EC16F7EE@spinnakernet.com>
Brian O'Keefe wrote:
>
> I'm not sure yet if this is a true bug, but it sure seems like one...
>
> I've got a 2-processor machine that I'm using as an NFS client. I've
> written some code that is doing a boatload of NFS reads from this
> client, locking whole files as read-only as I do each read. I've got
> multiple processes running the same code. Pretty regularly, I can get
> this client machine to lock up. I've scoured the web looking for hints
> about what might be wrong, and I'm using a kgdb to debug this from a
> remote machine.
Kernel 2.4.0.
Brian,
linux-smp@vger is rather dead. You certainly won't get the
attention of the NFS developers there.
>From your excellent description it seems that the kernel
is calling schedule() with nfs_flushd_lock held. The same
CPU comes back into the NFS code on behalf of a different task,
hits the lock and it's lights out.
This is pretty hard to track down. One approach is
to put
show_stack(p->thread.esp);
right at the end of kernel/sched.c:show_task(). When the deadlock
happens, type ALT-SYSRQ-T, pray like hell that the debug output
makes it to disk. Reboot, feed the logs into ksymoops, see which
task is sleeping within the NFS code.
The alternative is to read the code :)
There appear to be two places where the NFS client code can
deadlock:
nfs_reqlist_init()
{
spin_lock(&nfs_flushd_lock);
rpc_new_task->
rpc_allocate->
->kmalloc(GFP_RPC) (__GFP_WAIT is true)
inode_remove_flushd()
{
spin_lock(&nfs_flushd_lock);
iput(inode)->
nfs_delete_inode->
delete_inode->
wait_on_inode
truncate_inode_pages->
truncate_list_pages->
wait_on_page
The latter is most likely the problem. Here's a patch - please
test. The inode_remove_flush() change is correct. Not so
sure about the nfs_reqlist_init() change.
--- linux-2.4.0/fs/nfs/flushd.c Sat Jun 24 15:39:46 2000
+++ linux-akpm/fs/nfs/flushd.c Wed Jan 10 19:25:44 2001
@@ -55,7 +55,7 @@
/*
* Spinlock
*/
-spinlock_t nfs_flushd_lock = SPIN_LOCK_UNLOCKED;
+static spinlock_t nfs_flushd_lock = SPIN_LOCK_UNLOCKED;
/*
* Local function declarations.
@@ -71,6 +71,7 @@
int status = 0;
dprintk("NFS: writecache_init\n");
+ task = rpc_new_task(server->client, NULL, RPC_TASK_ASYNC);
spin_lock(&nfs_flushd_lock);
cache = server->rw_requests;
@@ -79,7 +80,6 @@
/* Create the RPC task */
status = -ENOMEM;
- task = rpc_new_task(server->client, NULL, RPC_TASK_ASYNC);
if (!task)
goto out_unlock;
@@ -195,7 +195,9 @@
if (*q) {
*q = inode->u.nfs_i.hash_next;
NFS_FLAGS(inode) &= ~NFS_INO_FLUSH;
+ spin_unlock(&nfs_flushd_lock);
iput(inode);
+ return;
}
out:
spin_unlock(&nfs_flushd_lock);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-01-10 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A5B42BF.EC16F7EE@spinnakernet.com>
2001-01-10 8:27 ` Andrew Morton [this message]
2001-01-10 9:47 ` Trond Myklebust
2001-01-10 12:42 ` Brian O'Keefe
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=3A5C1CF2.170E0A04@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=okeefe@spinnakernet.com \
--cc=trond.myklebust@fys.uio.no \
/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
Powered by JetHome