From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ion Badulescu <ionut@badula.org>
Cc: nfs@lists.sourceforge.net
Subject: oops in the 2.4.20-NFSALL sunrpc code
Date: Fri, 13 Dec 2002 16:42:40 +0100 [thread overview]
Message-ID: <15865.65520.122137.890996@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0212131002500.15305-100000@moisil.badula.org>
>>>>> " " == Ion Badulescu <ionut@badula.org> writes:
> It's caused, from what I can tell, by task->tk_client being
> NULL in xprt_timer() at the time it is dereferenced. Looks like
> a race condition, probably facilitated by the SMP kernel.
It's definitely not a race condition: Every new task is supposed to
call rpc_init_task() prior to calling rpc_execute(). This
again initializes task->tk_client once and for all. It is never
allowed to change.
There is only one exception to the above rule, namely nfs_flushd,
(which can never stray into net/sunrpc/xprt.c).
All I can say about this one is that it doesn't look like anything
I've come across on any other setups. Have you tried to reproduce it
on an actual 2.4.20 kernel?
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-12-13 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 15:22 oops in the 2.4.20-NFSALL sunrpc code Ion Badulescu
2002-12-13 15:42 ` Trond Myklebust [this message]
2002-12-13 17:05 ` Ion Badulescu
2002-12-13 17:39 ` 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=15865.65520.122137.890996@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=ionut@badula.org \
--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.