From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: RE: linux 2.4.20 oops
Date: Tue, 29 Apr 2003 19:04:49 +0200 [thread overview]
Message-ID: <16046.45233.640294.228310@charged.uio.no> (raw)
In-Reply-To: <6440EA1A6AA1D5118C6900902745938E07D55598@black.eng.netapp.com>
>>>>> " " == Charles Lever <Lever> writes:
> the fix appears in 2.4.21-pre7, but was removed from
> 2.4.21-rc1. trond?
Huh? From the latest BK pull linux/net/sunrpc/sched.c
/*
* Delete any timer for the current task. Because we use
del_timer_sync(),
* this function should never be called while holding rpc_queue_lock.
*/
static inline void
rpc_delete_timer(struct rpc_task *task)
{
dprintk("RPC: %4d deleting timer\n", task->tk_pid);
del_timer_sync(&task->tk_timer);
}
So AFAICS it is still there. I certainly have no quarrel with that
patch. I hit upon the same problem + fix in a different bug-report at
~ the same time.
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-29 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 16:56 linux 2.4.20 oops Lever, Charles
2003-04-29 17:04 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-29 17:31 Lever, Charles
2003-04-29 17:24 Lever, Charles
[not found] <6440EA1A6AA1D5118C6900902745938E07D5559A@black.eng.netapp.com>
2003-04-29 17:21 ` Trond Myklebust
2003-04-29 9:46 Brasseur Valéry
2003-04-29 9:18 Brasseur Valéry
2003-04-29 9:44 ` Danny Smith
2003-04-29 16:31 ` Philippe Troin
2003-04-29 16:44 ` Danny Smith
2003-04-29 16:53 ` Trond Myklebust
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=16046.45233.640294.228310@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.