public inbox for linux-kernel@vger.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: Mon, 06 Nov 2006 21:08:56 +0800	[thread overview]
Message-ID: <1162818536.10271.20.camel@localhost> (raw)
In-Reply-To: <20061106214252.3B37.Y-GOTO@jp.fujitsu.com>

On Mon, 2006-11-06 at 21:47 +0900, Yasunori Goto wrote:
> Hi.
> 
> > I've checked this and this is not the only problem.
> > Also autofs4_ is called with s->s_root NULL in this case.
> > 
> > The attached patch ensures that the autofs filesystem is initialized to be 
> > catatonic until super block setup is complete which avoids the problem 
> > above. It also checks s->s_root before use.
> > 
> > Could someone seeing this problem try this patch out please.
> 
> Sorry for late response. I was off.
> I tested your patch on my box. It worked well.

Thanks.

Unfortunately, I've got a couple of other problems.

In my testing I managed to panic the kernel further on, somewhere in
selinux. The scenario is slightly different though, running autofs
version 5 against a version 4 module. I really can't see why, all the
references look OK. I'm not sure what can be done it either as we're
talking about an older kernel anyway.

My other problem is I can't get my -mm kernel to build atm so I can't
really test further. I'm sure that will change soon.

Ian



      reply	other threads:[~2006-11-06 13:09 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
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 [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=1162818536.10271.20.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox