All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ed L. Cashin" <ecashin@coraid.com>
To: nfs@lists.sourceforge.net
Subject: nfsd pointer in __d_lookup
Date: Thu, 1 Jun 2006 16:12:57 -0400	[thread overview]
Message-ID: <20060601201257.GE20253@coraid.com> (raw)

Hi.  On an x86_64 machine, the trace below appears in the system logs
just before NFS service becomes unavailable (until a reboot).

I'm working on getting more specifics, but this machine is exporting
an XFS on an LVM logical volume on one or more AoE device.  The aoe
driver in use is not the one in 2.6.16.18 (it's aoe6-23), but I'm
asking the end user to verify that this still happens with the aoe
driver in 2.6.16.18.

Meanwhile, I'm hoping that the trace below will look familiar to
someone.  It looks to me like a 32-bit all-ones value might have been
put into a 64-bit variable by mistake.

  Unable to handle kernel paging request at 00000000ffffffff RIP: 
  <ffffffff80179456>{__d_lookup+216}
  PGD 3d29d067 PUD 0 
  CPU 0 
  Modules linked in: ipv6 nfsd lockd nfs_acl sunrpc xfs exportfs dm_mod aoe i2c_i801 i2c_core piix md_mod rtc psmouse unix
  Pid: 2535, comm: nfsd Not tainted 2.6.16.18-c1 #8
  RIP: 0010:[__d_lookup+216/253] <ffffffff80179456>{__d_lookup+216}
  RSP: 0018:ffff81003e6dd958  EFLAGS: 00010206
  RAX: 00000000ffffffff RBX: ffff81003ca443c0 RCX: 0000000000000011
  RDX: 0000000000014faf RSI: 00c3df84ef894faf RDI: ffff810037552080
  RBP: 00000000ffffffff R08: 0000000000000000 R09: 0000000000000000
  R10: 000000000000000c R11: 0000000000000130 R12: ffff810037552080
  R13: ffff81003e6dd9c8 R14: 00000000d8788a14 R15: 000000000000000c
  FS:  00002b9fd29cbae0(0000) GS:ffffffff803e6000(0000) knlGS:0000000000000000
  CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
  CR2: 00000000ffffffff CR3: 000000003d29c000 CR4: 00000000000006e0
  Process nfsd (pid: 2535, threadinfo ffff81003e6dc000, task ffff81003f15f790)
  Stack: ffff81003c1e2be2 0000000000000000 ffff810037552080 ffff81003e6dd9c8 
         0000000000000000 ffff8100375547f8 ffff81003c53d140 ffffffff80170839 
         000000000000000c ffff810037552080 
  Call Trace: <ffffffff80170839>{__lookup_hash+96} <ffffffff80170935>{lookup_one_len+95}
         <ffffffff88116998>{:nfsd:compose_entry_fh+203} <ffffffff88119121>{:nfsd:encode_entry+453}
         <ffffffff88119431>{:nfsd:nfs3svc_encode_entry_plus+11}
         <ffffffff880ae26d>{:xfs:linvfs_readdir+325} <ffffffff88119426>{:nfsd:nfs3svc_encode_entry_plus+0}
         <ffffffff88119426>{:nfsd:nfs3svc_encode_entry_plus+0}
         <ffffffff801747de>{vfs_readdir+90} <ffffffff80163cdf>{default_llseek+0}
         <ffffffff88119426>{:nfsd:nfs3svc_encode_entry_plus+0}
         <ffffffff8810ebc4>{:nfsd:nfsd_readdir+108} <ffffffff88116391>{:nfsd:nfsd3_proc_readdirplus+244}
         <ffffffff8810b3c2>{:nfsd:nfsd_dispatch+221} <ffffffff880d6360>{:sunrpc:svc_process+975}
         <ffffffff802c652f>{__down_read+18} <ffffffff8810b648>{:nfsd:nfsd+451}
         <ffffffff8012c278>{do_exit+2054} <ffffffff8010b702>{child_rip+8}
         <ffffffff8810b485>{:nfsd:nfsd+0} <ffffffff8010b6fa>{child_rip+0}


-- 
  Ed L Cashin <ecashin@coraid.com>


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2006-06-01 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 20:12 Ed L. Cashin [this message]
2006-06-02 11:36 ` nfsd pointer in __d_lookup Neil Brown
2006-06-02 15:37   ` Ed L. Cashin
2006-06-04 23:31     ` Neil Brown

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=20060601201257.GE20253@coraid.com \
    --to=ecashin@coraid.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.