From: Jeff Dike <jdike@addtoit.com>
To: Paolo Giarrusso <blaisorblade_personal@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Gerd Knorr <kraxel@bytesex.org>
Subject: Re: [uml-devel] Managing 2.6 merge - url for the patches sent to merge
Date: Mon, 20 Sep 2004 23:21:42 -0400 [thread overview]
Message-ID: <200409210321.i8L3LgdR015667@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 20 Sep 2004 20:30:49 +0200." <200409202030.49422.blaisorblade_personal@yahoo.it>
blaisorblade_personal@yahoo.it said:
> Don't use uml-use-va_end.patch, it breaks UML on rebooting.
How? That patch looks completely safe to me.
Rebooting is broken (in tt mode anyway) because the file lock on the root
ubd file descriptor isn't dropped. Mysteriously, setting that descriptor
CLOEXEC doesn't seem to help.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-09-21 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 17:44 [uml-devel] Managing 2.6 merge Paolo Giarrusso
2004-09-18 20:52 ` Jeff Dike
2004-09-19 9:43 ` Paolo Giarrusso
2004-09-19 11:38 ` Paolo Giarrusso
2004-09-20 9:38 ` Gerd Knorr
2004-09-20 18:30 ` [uml-devel] Managing 2.6 merge - url for the patches sent to merge Paolo Giarrusso
2004-09-21 3:21 ` Jeff Dike [this message]
2004-09-21 18:01 ` Paolo Giarrusso
2004-09-21 19:11 ` Henrik Nordstrom
2004-09-21 12:37 ` Gerd Knorr
2004-09-21 17:55 ` Paolo Giarrusso
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=200409210321.i8L3LgdR015667@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_personal@yahoo.it \
--cc=kraxel@bytesex.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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