Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: David Shaw <dshaw-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	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: Thu, 29 Jan 2009 10:34:01 -0500	[thread overview]
Message-ID: <20090129153401.GB24712@fieldses.org> (raw)
In-Reply-To: <C63C470C-C086-4B70-ADD8-6BFDFA8DEF5F-wh+mT2OhP0WF0gnf/s2wvA@public.gmane.org>

On Thu, Jan 29, 2009 at 09:00:56AM -0500, David Shaw wrote:
> On Jan 27, 2009, at 5:56 PM, J. Bruce Fields wrote:
>
>> On Tue, Jan 27, 2009 at 05:09:40PM -0500, bfields wrote:
>>> On Tue, Jan 27, 2009 at 08:48:41PM +0100, Miklos Szeredi wrote:
>>>>
>>>> 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.
>>
>> Might have been 2da2c21d7508d34bc6d600df665d84871b65d2b9 "Add a
>> reference to sunrpc in svc_addsock" ?
>
> Very possibly.  That fix went into 2.6.28, and I can confirm that the  
> problem does not reoccur under 2.6.28.2.
>
> Thanks for your help!

Thanks for the confirmation.--b.

      parent reply	other threads:[~2009-01-29 15:34 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
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               ` J. Bruce Fields [this message]

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=20090129153401.GB24712@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox