Subject: Re: [BUG] 2.6.19-rc3 autofs crash on my IA64 box
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
In-Reply-To: <20061106214252.3B37.Y-GOTO@jp.fujitsu.com>
References: <20061102183020.446D.Y-GOTO@jp.fujitsu.com>
	 <Pine.LNX.4.64.0611031610070.7573@raven.themaw.net>
	 <20061106214252.3B37.Y-GOTO@jp.fujitsu.com>
Content-Type: text/plain
Date: Mon, 06 Nov 2006 21:08:56 +0800
Message-Id: <1162818536.10271.20.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1303
Lines: 36

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/