From: William Lee Irwin III <wli@holomorphy.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@digeo.com>,
Linus Torvalds <torvalds@transmeta.com>,
zwane@holomorphy.com, cw@f00f.org, linux-kernel@vger.kernel.org,
mbligh@aracnet.com
Subject: Re: doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots)
Date: Thu, 20 Feb 2003 14:42:05 -0800 [thread overview]
Message-ID: <20030220224205.GD29983@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302202303400.4661-100000@localhost.localdomain>
On Thu, 20 Feb 2003, Andrew Morton wrote:
>> Fixes two deadlocks in the scheduler exit path:
>> 1: We're calling mmdrop() under spin_lock_irq(&rq->lock). But mmdrop
>> calls vfree(), which calls smp_call_function().
On Thu, Feb 20, 2003 at 11:04:41PM +0100, Ingo Molnar wrote:
> this has been fixed in the -F3 scheduler patch.
Not quite. It leaks mm's because schedule_tail() isn't cleaning
up rq->prev_mm.
-- wli
next prev parent reply other threads:[~2003-02-20 22:33 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302201830580.474-100000@localhost.localdomain>
2003-02-20 18:01 ` doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots) Linus Torvalds
2003-02-20 18:23 ` Linus Torvalds
2003-02-20 19:36 ` Ingo Molnar
2003-02-20 19:53 ` Ingo Molnar
2003-02-20 19:57 ` Ingo Molnar
2003-02-20 20:14 ` Ingo Molnar
2003-02-20 20:17 ` Linus Torvalds
2003-02-20 20:50 ` Andrew Morton
2003-02-20 22:04 ` Ingo Molnar
2003-02-20 22:42 ` William Lee Irwin III [this message]
2003-02-21 7:05 ` Ingo Molnar
2003-02-20 22:00 ` Ingo Molnar
2003-02-20 22:32 ` Linus Torvalds
2003-02-20 22:40 ` Linus Torvalds
2003-02-20 22:45 ` Linus Torvalds
2003-02-20 22:57 ` John Levon
2003-02-20 23:21 ` Ingo Molnar
2003-02-20 23:36 ` Linus Torvalds
2003-02-21 7:00 ` Ingo Molnar
2003-02-21 15:05 ` Linus Torvalds
2003-02-20 19:00 ` Ingo Molnar
2003-02-18 23:01 Linux v2.5.62 --- spontaneous reboots Chris Wedgwood
2003-02-19 23:35 ` doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots) Linus Torvalds
2003-02-20 2:22 ` Zwane Mwaikambo
2003-02-20 2:26 ` William Lee Irwin III
2003-02-20 2:55 ` Zwane Mwaikambo
2003-02-20 3:15 ` William Lee Irwin III
2003-02-20 4:52 ` Linus Torvalds
2003-02-20 5:07 ` William Lee Irwin III
2003-02-20 6:05 ` Zwane Mwaikambo
2003-02-20 11:46 ` Ingo Molnar
2003-02-20 12:12 ` William Lee Irwin III
2003-02-20 12:33 ` Ingo Molnar
2003-02-20 14:03 ` Zwane Mwaikambo
2003-02-20 14:00 ` Zwane Mwaikambo
2003-02-20 15:43 ` Linus Torvalds
2003-02-20 15:52 ` Ingo Molnar
2003-02-20 16:11 ` Martin J. Bligh
2003-02-20 16:54 ` Linus Torvalds
2003-02-20 17:24 ` Jeff Garzik
2003-02-20 21:21 ` Alan Cox
2003-02-20 20:20 ` Linus Torvalds
2003-02-20 20:23 ` Martin J. Bligh
2003-02-20 20:42 ` William Lee Irwin III
2003-02-20 20:51 ` Linus Torvalds
2003-02-27 18:50 ` Randy.Dunlap
2003-02-27 19:39 ` Muli Ben-Yehuda
2003-02-27 19:47 ` Randy.Dunlap
2003-03-02 6:12 ` Keith Owens
2003-02-27 23:32 ` Randy.Dunlap
2003-02-20 23:09 ` Chris Wedgwood
2003-02-20 16:44 ` Ingo Molnar
2003-02-20 20:13 ` Chris Wedgwood
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=20030220224205.GD29983@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.com \
--cc=zwane@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox