Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Aaron Porter <atporter@primate.net>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: NFS Oops 2.6.20.14
Date: Thu, 21 Jun 2007 17:40:20 -0400	[thread overview]
Message-ID: <467AF044.1090306@redhat.com> (raw)
In-Reply-To: <20070618200507.GS6601@primate.net>

On 06/18/2007 04:05 PM, Aaron Porter wrote:
> 	Reproducable, every time nfs-kernel-server exits:
> 
> nfsd: unexporting all filesystems
> BUG: unable to handle kernel paging request at virtual address 6b6b6b6f
>  printing eip:
> f92a7751
> *pde = 6b6b6b6b
> Oops: 0000 [#1]
> PREEMPT SMP 
> Modules linked in: xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables x_tables nfs nfsd exportfs lockd sunrpc capability commoncap ipv6 ohci_hcd usbcore amd_rng rng_core i2c_amd8111 generic amd74xx shpchp pci_hotplug ide_scsi w83627hf eeprom lm85 hwmon_vid i2c_isa i2c_amd756 i2c_core rtc unix
> CPU:    0
> EIP:    0060:[<f92a7751>]    Not tainted VLI
> EFLAGS: 00010202   (2.6.20.14-20070612 #2)
> EIP is at cache_clean+0x101/0x1e6 [sunrpc]
> eax: 00000000   ebx: 6b6b6b6b   ecx: 00000001   edx: f92eb940
> esi: dfd9e800   edi: 00000000   ebp: efc7e000   esp: f56bbf84
> ds: 007b   es: 007b   ss: 0068
> Process nfsd (pid: 2856, ti=f56ba000 task=c74daaa0 task.ti=f56ba000)
> Stack: f92eb940 f70ddd50 00000000 f92a7880 f92a78aa f70ddd24 f92cae61 f92a1b8c 
>        f92a1fe1 00000009 00000000 00000009 00000000 f92c36b2 f92dd07d efc7e000 
>        fffffeff ffffffff fffffef8 ffffffff f92c3448 00000000 00000000 00000000 
> Call Trace:
>  [<f92a7880>] cache_flush+0xc/0x1f [sunrpc]
>  [<f92a78aa>] cache_purge+0x17/0x20 [sunrpc]
>  [<f92cae61>] nfsd_export_flush+0x14/0x28 [nfsd]
>  [<f92a1b8c>] svc_destroy+0x96/0x100 [sunrpc]
>  [<f92a1fe1>] svc_exit_thread+0x69/0x7d [sunrpc]
>  [<f92c36b2>] nfsd+0x26a/0x27b [nfsd]
>  [<f92c3448>] nfsd+0x0/0x27b [nfsd]
>  [<c010364b>] kernel_thread_helper+0x7/0x10

  25:   8b 15 60 ea 2b f9         mov    0xf92bea60,%edx
   0:   8b 43 04                  mov    0x4(%ebx),%eax   <=====
   3:   39 42 54                  cmp    %eax,0x54(%edx)
   6:   7e 04                     jle    c <_EIP+0xc>
   8:   40                        inc    %eax
   9:   89 42 54                  mov    %eax,0x54(%edx)

net/sunrpc/cache.c::cache_clean():
                cp = & current_detail->hash_table[current_index];
                ch = *cp;
                for (; ch; cp= & ch->next, ch= *cp) {
=> ch has been freed ==> if (current_detail->nextcheck > ch->expiry_time)
                                current_detail->nextcheck = ch->expiry_time+1;



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

           reply	other threads:[~2007-06-21 21:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20070618200507.GS6601@primate.net>]

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=467AF044.1090306@redhat.com \
    --to=cebbert@redhat.com \
    --cc=atporter@primate.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox