From: Jeff Dike <jdike@karaya.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7pre8aa1
Date: Sun, 22 Jul 2001 22:49:42 -0500 [thread overview]
Message-ID: <200107230349.WAA04057@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Mon, 23 Jul 2001 03:11:46 +0200." <20010723031146.D23517@athlon.random>
andrea@suse.de said:
> I should have said "compiles" fine (not "works" fine :).
2.4.6 "works" fine :-)
I just finished fixing 2.4.7. My fixes are similar to yours (I moved
stext rather than moving .data.init).
> __initdata is broken in uml and the kernel deadlocks because the wait
> list is empty in complete() despite wait_for_completion actually
> registered correctly into it. This because wait_for_completion runs in
> a different address space than complete() and the virtual memory is
> not shared across the two address spaces (it is not rempped in a
> MAP_SHARED so it generates a cow). The registration is basically only
> private to the entity that is registrating and it will never get
> visible to the waker task that will do nothing. This is a severe bug
> not just for the completion code in 2.4.7.
Nice debugging, btw. I spent an hour this morning chasing that problem.
My 2.4.7 patch is available from the usual places:
http://ftp.nl.linux.org/pub/uml/uml-patch-2.4.7-1.bz2
http://uml-pub.ists.dartmouth.edu/uml/uml-patch-2.4.7-1.bz2
http://prdownloads.sourceforge.net/user-mode-linux/uml-patch-2.4.7-1.bz2
Jeff
next prev parent reply other threads:[~2001-07-23 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 22:45 2.4.7pre8aa1 Jeff Dike
2001-07-20 1:37 ` 2.4.7pre8aa1 Andrea Arcangeli
2001-07-20 0:42 ` 2.4.7pre8aa1 Jeff Dike
2001-07-23 1:11 ` 2.4.7pre8aa1 Andrea Arcangeli
2001-07-23 3:49 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-19 18:38 2.4.7pre8aa1 Andrea Arcangeli
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=200107230349.WAA04057@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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