Re: 2.6.23-mm1 - autofs broken

From: Rik van Riel
Date: Sat Oct 20 2007 - 01:54:32 EST


On Fri, 19 Oct 2007 22:39:00 -0700
Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Sat, 20 Oct 2007 01:13:10 -0400 Rik van Riel <riel@xxxxxxxxxx>
> wrote:
>
> > On Thu, 11 Oct 2007 21:31:26 -0700
> > Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/
> > >
> > > - I've been largely avoiding applying anything since rc8-mm2 in an
> > > attempt to stabilise things for the 2.6.23 merge.
> >
> > Between rc8-mm2 and 2.6.23-mm1, autofs stopped working in the
> > -mm kernel.
> >
> > Instead of mounting my home directory, I get these messages in
> > /var/log/messages:
> >
> > Oct 20 00:38:52 kenny automount[2293]: cache_readlock: mapent cache
> > rwlock lock failed
> > Oct 20 00:38:52 kenny automount[2293]: unexpected pthreads error:
> > 11 at 65 in cache.c
> >
> > I am not sure if this is due to autofs changes or changes in some
> > other code that was merged. If you can think of any suspicious
> > change that I should test, please let me know.
>
> I don't think anything changed in autofs in that period. I'd be
> suspecting the r-o-bind-mounts patches, but they didn't change much
> in that time either.
>
> Does current mainline work OK? If so, pretty much the only thing in
> that area left unmerged is r-o-bind-mounts and hch's exportfs stuff.

Yes, 2.6.23 mainline works fine.

--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/