From: Andrew Morton <akpm@osdl.org>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: 2.6.10-rc1-mm5 [u]
Date: Sat, 13 Nov 2004 15:24:57 -0800 [thread overview]
Message-ID: <20041113152457.6cb0fedb.akpm@osdl.org> (raw)
In-Reply-To: <1100384533.12195.3.camel@nosferatu.lan>
"Martin Schlemmer [c]" <azarah@nosferatu.za.org> wrote:
>
> > Could you please try:
> >
> > wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm5/broken-out/futex_wait-fix.patch
> > patch -R -p1 < futex_wait-fix.patch
> >
> > the retest?
>
> Yep, this seems to fix it (usually one thread at least have already hung
> at start for evo, now fine after a few mail fetches).
OK, thanks.
> Is this a regression, or as in the other thread an issue with evolution
> that should be fixed ? (Note: gnome-btdownload also seemed to hang
> overnight with -mm[45], but I do not know if its related)
Don't know. It's hard to see why that patch would cause gross misbehaviour
in evolution and apache. We may have to just revert it and take another
look at the problem which it fixes.
One thing I do note which is unrelated to this problem is that futex_wait()
does get_user() inside down_read(mmap_sem). But a fault will do a second
down_read(). And doing down_read() twice from within the same thread is a
bug, because an intervening down_write() from another thread will cause
deadlock.
next prev parent reply other threads:[~2004-11-13 23:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 9:23 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:09 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:11 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:24 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:45 ` 2.6.10-rc1-mm5 Brice Goglin
2004-11-11 11:00 ` 2.6.10-rc1-mm5 Stefano Rivoir
2004-11-11 11:13 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 11:04 ` 2.6.10-rc1-mm5 Markus Trippelsdorf
2004-11-11 11:08 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 21:55 ` 2.6.10-rc1-mm5 Martin J. Bligh
2004-11-11 22:14 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 9:27 ` 2.6.10-rc1-mm5 Jens Axboe
2004-11-11 22:41 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 10:50 ` [PATCH] Fix SHMEM options David Howells
2004-11-12 16:45 ` Christoph Hellwig
2004-11-11 12:11 ` 2.6.10-rc1-mm5: yenta_socket issue Rafael J. Wysocki
2004-11-11 12:21 ` Andrew Morton
2004-11-11 12:43 ` Rafael J. Wysocki
2004-11-12 3:55 ` Rusty Russell
2004-11-11 16:50 ` 2.6.10-rc1-mm5: REISER4_LARGE_KEY is still selectable Adrian Bunk
2004-11-12 7:07 ` Vladimir Saveliev
2004-11-12 13:23 ` Adrian Bunk
2004-11-12 16:16 ` DaMouse
2004-11-12 16:37 ` Vladimir Saveliev
2004-11-12 17:15 ` Adrian Bunk
2004-12-11 17:25 ` Hans Reiser
2004-11-11 21:45 ` Reiser{3,4}: problem with the copyright statement Adrian Bunk
2004-11-11 21:59 ` Linus Torvalds
2004-11-12 16:47 ` Christoph Hellwig
2004-11-12 17:06 ` Christoph Hellwig
2004-11-12 17:11 ` Adrian Bunk
2004-11-12 17:13 ` Christoph Hellwig
2004-11-12 19:33 ` Hans Reiser
2004-11-11 22:51 ` Stephen Pollei
2004-11-12 2:08 ` Zan Lynx
2004-11-11 23:28 ` 2.6.10-rc1-mm5: reiser4: print_clog in debug.c useless? Adrian Bunk
2004-11-12 2:39 ` 2.6.10-rc1-mm5: strange fs/reiser4/linux-5_reiser4_syscall.patch Adrian Bunk
2004-11-12 14:30 ` [patch] 2.6.10-rc1-mm5: some reiser4 cleanups Adrian Bunk
2004-11-12 19:00 ` 2.6.10-rc1-mm5 Alexander Nyberg
2004-11-13 0:11 ` 2.6.10-rc1-mm5 Greg KH
2004-11-13 17:55 ` 2.6.10-rc1-mm5 [u] Martin Schlemmer [c]
2004-11-13 21:16 ` Martin Schlemmer [c]
2004-11-13 21:22 ` Andrew Morton
2004-11-13 22:19 ` Jedi/Sector One
2004-11-13 22:22 ` Martin Schlemmer [c]
2004-11-13 23:24 ` Andrew Morton [this message]
2004-11-14 0:07 ` Martin Schlemmer [c]
2004-11-14 9:10 ` Jamie Lokier
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=20041113152457.6cb0fedb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=seto.hidetoshi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.