Date: Sat, 14 Jan 2006 03:34:41 -0800
From: Andrew Morton <akpm@osdl.org>
To: "P. Christeas" <p_christ@hol.gr>
Cc: hch@lst.de, linux-kernel@vger.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: Regression in Autofs, 2.6.15-git
Message-Id: <20060114033441.0d80b9f2.akpm@osdl.org>
In-Reply-To: <200601140217.56724.p_christ@hol.gr>
References: <200601140217.56724.p_christ@hol.gr>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1690
Lines: 38

"P. Christeas" <p_christ@hol.gr> wrote:
>
> I had been testing some other thing in the kernel, when I noticed that the 
> commit (in Linus' tree) given below makes *autofs4* crash.
> It does crash with a hard oops whenever I try to enter a /net/host/... address 
> in konqueror's location bar.
> Is this a known issue or should I provide more information?
> 
> 
> commit fc33a7bb9c6dd8f6e4a014976200f8fdabb3a45c
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Mon Jan 9 20:52:17 2006 -0800
> 
>     [PATCH] per-mountpoint noatime/nodiratime
> 
>     Turn noatime and nodiratime into per-mount instead of per-sb flags.
> 
>     After all the preparations this is a rather trivial patch.  The mount code
>     needs to treat the two options as per-mount instead of per-superblock, and
>     touch_atime needs to be changed to check the new MNT_ flags in addition to
>     the MS_ flags that are kept for filesystems that are always
>     noatime/nodiratime but not user settable anymore.  Besides that core code
>     only nfs needed an update because it's leaving atime updates to the server
>     and thus sets the S_NOATIME flag on every inode, but needs to know whether
>     it's a real noatime mount for an getattr optimization.
> 
>     While we're at it I've killed the IS_NOATIME/IS_NODIRATIME macros that 
> were
>     only used by touch_atime.

Thanks for working that out.

It works for me.  Are you able to capture the oops output?
-
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/