All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: "bibo,mao" <bibo.mao@intel.com>,
	David Howells <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.19-rc3 autofs crash on my IA64 box
Date: Thu, 02 Nov 2006 18:21:16 +0800	[thread overview]
Message-ID: <1162462876.6980.8.camel@localhost> (raw)
In-Reply-To: <20061102183020.446D.Y-GOTO@jp.fujitsu.com>

On Thu, 2006-11-02 at 18:51 +0900, Yasunori Goto wrote:
> Hello.
> 
> > hi,
> >   2.6.19-rc3 kernel crashes on my IA64 box, it seems the problem
> > of autofs fs. I debug this problem, if autofs kernel does not
> > match daemon version, it will call autofs_catatonic_mode.
> > But at that time sbi->pipe is NULL.
> > 
> > void autofs_catatonic_mode(struct autofs_sb_info *sbi)
> > {
> >    .........
> >    fput(sbi->pipe);        /* Close the pipe */
> > 	^^^^^^^^^^^^
> >  	sbi->pipe seems NULL;
> >    autofs_hash_dputall(&sbi->dirhash); /* Remove all dentry pointers */
> > }
> > 
> 
> My box crashed too.
> 
> Following fix does not seem enough.
> http://marc.theaimsgroup.com/?l=linux-kernel&m=116110204104327&w=2

I'm not surprised it addresses a completely different problem.

> If version does not match at autofs_fill_super(), then sbi->pipe
> is not set yet.
> I suppose something like following patch is necessary.

At least but I'll need to check a bit further into this and the autofs4
module should be updated in a similar manner. Even though it will
support the latest requested version it should still handle this error
case.

Ian



  reply	other threads:[~2006-11-02 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01  8:02 [BUG] 2.6.19-rc3 autofs crash on my IA64 box bibo,mao
2006-11-02  9:51 ` Yasunori Goto
2006-11-02 10:21   ` Ian Kent [this message]
2006-11-03  8:21   ` Ian Kent
2006-11-03  8:24     ` Ian Kent
2006-11-06 12:47     ` Yasunori Goto
2006-11-06 13:08       ` Ian Kent

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=1162462876.6980.8.camel@localhost \
    --to=raven@themaw.net \
    --cc=bibo.mao@intel.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=y-goto@jp.fujitsu.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.