From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Michael Gernoth <simigern@stud.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hanging NFS umounts with 2.4.27
Date: Fri, 05 Nov 2004 11:55:41 -0800 [thread overview]
Message-ID: <1099684541.19858.1.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20041105100237.GA27689@cip.informatik.uni-erlangen.de>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
fr den 05.11.2004 Klokka 11:02 (+0100) skreiv Michael Gernoth:
> Searching through the Changesets I found 1.1402.1.19:
> http://linux.bkbits.net:8080/linux-2.4/cset@1.1402.1.19
> After reverting this one, we have a stable umount-behaviour again.
>
Does the attached patch help at all?
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
[-- Attachment #2: linux-2.4.28-fix_unlink.dif --]
[-- Type: text/plain, Size: 792 bytes --]
NFS: Always wake up tasks that are waiting on the sillyrenamed file to
complete.
---
unlink.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
Index: linux-2.4.28-rc1/fs/nfs/unlink.c
===================================================================
--- linux-2.4.28-rc1.orig/fs/nfs/unlink.c 2004-11-05 11:26:07.832922087 -0800
+++ linux-2.4.28-rc1/fs/nfs/unlink.c 2004-11-05 11:44:38.241824060 -0800
@@ -130,13 +130,14 @@ nfs_async_unlink_done(struct rpc_task *t
if (nfs_async_handle_jukebox(task))
return;
if (!dir)
- return;
+ goto out;
dir_i = dir->d_inode;
nfs_zap_caches(dir_i);
NFS_PROTO(dir_i)->unlink_done(dir, &task->tk_msg);
put_rpccred(data->cred);
data->cred = NULL;
dput(dir);
+out:
data->completed = 1;
wake_up(&data->waitq);
}
next prev parent reply other threads:[~2004-11-05 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 10:02 Michael Gernoth
2004-11-05 19:55 ` Trond Myklebust [this message]
2004-11-05 20:22 ` Michael Gernoth
2004-11-08 21:21 ` Michael Gernoth
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=1099684541.19858.1.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=simigern@stud.uni-erlangen.de \
/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®