From: Dipankar Sarma <dipankar@in.ibm.com>
To: John M Flinchbaugh <glynis@butterfly.hjsoft.com>
Cc: linux-kernel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Linus Torvalds <torvalds@transmeta.com>,
Maneesh Soni <maneesh@in.ibm.com>
Subject: Re: 2.5.70-bk16: nfs crash
Date: Thu, 12 Jun 2003 19:22:54 +0530 [thread overview]
Message-ID: <20030612135254.GA2482@in.ibm.com> (raw)
In-Reply-To: <20030612125630.GA19842@butterfly.hjsoft.com>
On Thu, Jun 12, 2003 at 12:57:26PM +0000, John M Flinchbaugh wrote:
> running 2.5.70-bk16, i got this error and hang. sysrq worked for
> reboot, etc.
>
> it apparently crashed when it mounted an nfs export from a 2.4.18 box,
> and tried to mv a file. i doubt it matters, but the nic is an
> orinoco_cs wireless card. thanks.
>
> Jun 12 02:00:04 density kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
> Jun 12 02:00:04 density kernel: printing eip:
> Jun 12 02:00:04 density kernel: c0169ef1
> Jun 12 02:00:04 density kernel: *pde = 00000000
> Jun 12 02:00:04 density kernel: Oops: 0002 [#1]
> Jun 12 02:00:04 density kernel: CPU: 0
> Jun 12 02:00:04 density kernel: EIP: 0060:[<c0169ef1>] Not tainted
> Jun 12 02:00:04 density kernel: EFLAGS: 00010246
> Jun 12 02:00:04 density kernel: EIP is at d_move+0x51/0x250
> Jun 12 02:00:04 density kernel: eax: 00000000 ebx: cd5e6960 ecx: cd5e69d0 edx: 00000000
I am not supprised at all by this, I can see two csets in Linus' tree
that will definitely break dcache -
1. http://linux.bkbits.net:8080/linux-2.5/cset@1.1215.104.2?nav=index.html|ChangeSet@-2d
__d_drop() *must not* initialize d_hash fields. Lockfree lookup depends on
that. If __d_drop() needs to be allowed on an unhashed dentry, the right
thing to do would be to check for DCACHE_UNHASHED before unhashing. I will
submit a patch a little later to do this.
2. http://linux.bkbits.net:8080/linux-2.5/cset@1.1215.104.1?nav=index.html|ChangeSet@-2d
hlist poison patch is broken. list_del_rcu() and hlist_del_rcu()
*must not* re-initialize the pointers. Maneesh submitted a patch
earlier today that corrects this -
http://marc.theaimsgroup.com/?l=linux-kernel&m=105541206017154&w=2
Thanks
Dipankar
next prev parent reply other threads:[~2003-06-12 13:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 12:56 2.5.70-bk16: nfs crash John M Flinchbaugh
2003-06-12 13:52 ` Dipankar Sarma [this message]
2003-06-12 15:33 ` Dipankar Sarma
2003-06-12 15:35 ` Trond Myklebust
2003-06-12 15:53 ` Dipankar Sarma
2003-06-12 16:26 ` Trond Myklebust
2003-06-12 16:49 ` Linus Torvalds
2003-06-12 16:55 ` Linus Torvalds
2003-06-12 19:53 ` Dipankar Sarma
2003-06-13 5:24 ` Trond Myklebust
2003-06-13 5:50 ` Dipankar Sarma
2003-06-13 6:13 ` Trond Myklebust
2003-06-13 6:54 ` Dipankar Sarma
2003-06-13 6:06 ` Dipankar Sarma
2003-06-12 16:30 ` viro
2003-06-12 16:55 ` Dipankar Sarma
2003-06-12 15:49 ` Linus Torvalds
2003-06-12 16:05 ` Dipankar Sarma
2003-06-12 16:18 ` Linus Torvalds
2003-06-12 16:35 ` Dipankar Sarma
2003-06-12 16:47 ` Linus Torvalds
2003-06-13 12:48 ` Maneesh Soni
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=20030612135254.GA2482@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=torvalds@transmeta.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