From: Rik van Riel <riel@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
xemul@openvz.org, Ian Kent <raven@themaw.net>
Subject: Re: futex strangeness in 2.6.23-mm1/UML
Date: Mon, 22 Oct 2007 17:29:26 -0400 [thread overview]
Message-ID: <20071022172926.03ca122a@bree.surriel.com> (raw)
In-Reply-To: <E1Ik4Ch-000273-00@dorka.pomaz.szeredi.hu>
On Mon, 22 Oct 2007 22:48:51 +0200
Miklos Szeredi <miklos@szeredi.hu> wrote:
> > > I'm getting a process stuck in pthread_rwlock_wrlock(), even
> > > though it looks like the lock is not held by anybody.
> > >
> > > I think the last -mm was OK. Any ideas?
> > >
> > > If not, I'll go searching for the offending patch.
> >
> > I wonder if that's the same bug that's breaking autofs for me.
>
> Probably.
>
> > Oct 22 14:39:01 kenny automount[2299]: cache_readlock: mapent cache
> > rwlock lock failed
> > Oct 22 14:39:01 kenny automount[2299]: unexpected pthreads error:
> > 11 at 65 in cache.c
> >
> > I'm bisecting 2.6.23-mm1 today to find the problem patch, with
> > some luck I'll have it this afternoon.
> >
> > With the series applied up to
> > whitespace-fixes-task-exit-handling.patch things work.
> >
> > It breaks before kswapd-should-only-wait-on-io-if-there-is-io.patch
> >
> > That leaves only about 60-80 patches to look at :)
>
> OK, the first patch that breaks something for me is:
>
> pid-namespaces-move-alloc_pid-lower-in-copy_process.patch
Confirmed. That same patch is the point where the bisect
here starts breaking autofs.
Ian, it looks like the autofs code is innocent :)
--
"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
next prev parent reply other threads:[~2007-10-22 21:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 17:29 futex strangeness in 2.6.23-mm1/UML Miklos Szeredi
2007-10-22 18:53 ` Rik van Riel
2007-10-22 20:48 ` Miklos Szeredi
2007-10-22 21:29 ` Rik van Riel [this message]
2007-10-23 0:07 ` Rik van Riel
2007-10-23 0:16 ` Andrew Morton
2007-10-23 1:11 ` Rik van Riel
2007-10-23 1:38 ` Rik van Riel
2007-10-23 2:54 ` Ian Kent
2007-10-23 3:41 ` Jeff Dike
2007-10-23 7:36 ` Miklos Szeredi
2007-10-23 8:55 ` Pavel Emelyanov
2007-10-23 10:23 ` Miklos Szeredi
2007-10-23 13:52 ` Rik van Riel
2007-10-23 16:00 ` Andrew Morton
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=20071022172926.03ca122a@bree.surriel.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--cc=xemul@openvz.org \
/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