From: "J. Bruce Fields" <bfields@fieldses.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: dshaw-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org,
fuse-devel@lists.sourceforge.net, linux-nfs@vger.kernel.org,
Tom Tucker <tom@opengridcomputing.com>
Subject: Re: [fuse-devel] Kernel panic on 2.6.27.9 when NFS exporting fuse filesystem
Date: Tue, 27 Jan 2009 17:09:40 -0500 [thread overview]
Message-ID: <20090127220940.GE9151@fieldses.org> (raw)
In-Reply-To: <E1LRtvN-0003zf-8b-8f8m9JG5TPIdUIPVzhDTVZP2KDSNp7ea@public.gmane.org>
On Tue, Jan 27, 2009 at 08:48:41PM +0100, Miklos Szeredi wrote:
> [Forwarding to linux-nfs@ and sunrpc maintainers]
>
> On Mon, 26 Jan 2009, David Shaw wrote:
> > Hello,
> >
> > This is reasonably repeatable (i.e. not 100%, but certainly more than
> > 25%). The kernel is 2.6.27.9-159.fc10.i686.PAE (this is the most
> > recent Fedora 10 PAE kernel), and we're using fuse-2.8.0pre2 on the
> > userspace side. We are NFS-exporting the fuse filesystem. The
> > machine in question is a dual core Pentium D 2.8ghz with 4g of RAM.
>
> Can you try to reproduce this on a vanilla kernel, to exclude the
> possibility of a fedora patch being the culprit?
>
> > Occasionally, we get a sudden reboot. After attaching a serial cable,
> > we found this. It doesn't look directly fuse related from the
> > backtrace, but then again, we're not seeing any problems exporting a
> > regular (non-fuse) filesystem.
> >
> > Any thoughts?
>
> The BUG triggers in this __module_get() in svc_recv():
>
> /*
> * We know this module_get will succeed because the
> * listener holds a reference too
> */
> __module_get(newxpt->xpt_class->xcl_owner);
>
> Either the comment is wrong or something got corrupted.
>
> Tom, Bruce, any idea what could be causing this? It doesn't really
> look fuse related.
I seem to recall something being fixed recently there--I'll try to find
the commit id. In the mean time they might want to retest with the
latest kernel.
--b.
>
> Thanks,
> Miklos
>
> >
> > kernel BUG at include/linux/module.h:390!
> > invalid opcode: 0000 [#1] SMP
> > Modules linked in: nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs ipt_REDIRECT fuse ipmi_devintf ipmi_si ipmi_msghandler ipv6 iptable_nat nf_nat dm_multipath tg3 i2c_i801 libphy i3000_edac iTCO_wdt iTCO_vendor_support edac_core serio_raw pcspkr dcdbas ata_generic pata_acpi radeon drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
> >
> > Pid: 25841, comm: nfsd Not tainted (2.6.27.9-159.fc10.i686.PAE #1)
> > EIP: 0060:[<f8b02cc4>] EFLAGS: 00010246 CPU: 0
> > EIP is at svc_recv+0x3a4/0x6c6 [sunrpc]
> > EAX: 00000000 EBX: f8b13500 ECX: f8b13500 EDX: 00001000
> > ESI: f78b7d90 EDI: f35ea600 EBP: f21c8fbc ESP: f21c8f74
> > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> > Process nfsd (pid: 25841, ti=f21c8000 task=f4598000 task.ti=f21c8000)
> > Stack: c0893c80 0036ee80 f78b7000 f2549c04 f35ea61c f2549b80 f2549c00 f40a9600
> > f78b7000 f8bb1622 00000000 f4598000 c042d0f3 00100100 00200200 f3486b00
> > 00000000 f78b7000 f21c8fd0 f8bb16e5 f78b7000 f8bb1622 00000000 f21c8fe0
> > Call Trace:
> > [<f8bb1622>] ? nfsd+0x0/0x167 [nfsd]
> > [<c042d0f3>] ? default_wake_function+0x0/0xd
> > [<f8bb16e5>] ? nfsd+0xc3/0x167 [nfsd]
> > [<f8bb1622>] ? nfsd+0x0/0x167 [nfsd]
> > [<c0443973>] ? kthread+0x3b/0x61
> > [<c0443938>] ? kthread+0x0/0x61
> > [<c04098f7>] ? kernel_thread_helper+0x7/0x10
> > =======================
> > Code: 30 01 00 00 8b 57 04 89 f8 ff 52 04 85 c0 89 45 d4 0f 84 11 01 00 00 8b 00 8b 58 04 85 db 74 1f 89 d8 e8 56 d7 94 c7 85 c0 75 04 <0f> 0b eb fe 64 a1 04 c0 88 c0 c1 e0 07 ff 84 03 80 01 00 00 8b
> > EIP: [<f8b02cc4>] svc_recv+0x3a4/0x6c6 [sunrpc] SS:ESP 0068:f21c8f74
> > Kernel panic - not syncing: Fatal exception
> >
> > Thanks,
> >
> > David
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > SourcForge Community
> > SourceForge wants to tell your story.
> > http://p.sf.net/sfu/sf-spreadtheword
> > _______________________________________________
> > fuse-devel mailing list
> > fuse-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/fuse-devel
> >
next prev parent reply other threads:[~2009-01-27 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090126225404.GA27937@jabberwocky.com>
[not found] ` <20090126225404.GA27937-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org>
2009-01-27 19:48 ` [fuse-devel] Kernel panic on 2.6.27.9 when NFS exporting fuse filesystem Miklos Szeredi
[not found] ` <E1LRtvN-0003zf-8b-8f8m9JG5TPIdUIPVzhDTVZP2KDSNp7ea@public.gmane.org>
2009-01-27 22:09 ` J. Bruce Fields [this message]
2009-01-27 22:56 ` J. Bruce Fields
2009-01-29 14:00 ` David Shaw
[not found] ` <C63C470C-C086-4B70-ADD8-6BFDFA8DEF5F-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org>
2009-01-29 15:34 ` [fuse-devel] " J. Bruce Fields
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=20090127220940.GE9151@fieldses.org \
--to=bfields@fieldses.org \
--cc=dshaw-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tom@opengridcomputing.com \
/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.