From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net, hugh@mimosa.com,
Matt Zimmerman <mdz@debian.org>
Subject: Re: [uml-devel] unkillable UML threads
Date: Mon, 06 Oct 2003 21:09:05 -0400 [thread overview]
Message-ID: <3387.1065488945@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Your message of "Mon, 06 Oct 2003 17:18:54 EDT." <200310062119.h96LIsGj020742@ccure.karaya.com>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Jeff" == Jeff Dike <jdike@addtoit.com> writes:
Jeff> mcr@sandelman.ottawa.on.ca said:
>> FYI: This is without the skas patch, with a stock RH9 kernel on the
>> host.
>>
>> Any thoughts or coroboration would be appreciated. Clearly this is a
>> bug in the RH9 kernel.
Jeff> It could easily be a UML bug. I do have code which continues
Again, if any process becomes unkillable on *nix system, there is at
*least* a bug in the kernel. This should never be the case.
yes, there is likely also a bug in UML.
Jeff> threads so that they die properly, but it seems not to be happening
Jeff> here. Can you tell me how to reproduce it?
I don't have a formula. Hugh sees is pretty much at least once if not more
often in regression testing of FreeS/WAN.
Btw, I experience segment faults with 2.4.22-7 on a 2.4.20 host with skas
patch. Again, not trivially reproducible, but they do occur
frequently. Enough that since this is isn't RH9, I went back to 2.4.19-47,
which was pretty solid. I haven't tried things in between, but I could.
] Train travel features AC outlets with no take-off restrictions| firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat
iQCVAwUBP4ISMIqHRg3pndX9AQGFzAP8C6tutx3wvBYK5qKIlk9AgZ6J+HdcDtiG
C9/vLNtoBnMhU8t4i0W+gFEGvTHbL6uMi+dyuLMx4eKA4OvmJHRQVYid/aoe5P33
4tD8MhfWDqGgFGBj8m1gYX2v9psUo0PUwK6gBtmI6uu9DKyRi6bCYMqn0JXqFk+p
Tknwh/R0uMo=
=h6vh
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-10-07 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 12:40 [uml-devel] unkillable UML threads Michael Richardson
2003-09-24 14:30 ` Matt Zimmerman
2003-09-25 14:40 ` Michael Richardson
2003-10-06 21:18 ` Jeff Dike
2003-10-07 1:09 ` Michael Richardson [this message]
2003-10-07 3:20 ` Jeff Dike
2003-10-07 23:39 ` Michael Richardson
2003-10-11 4:15 ` Matt Zimmerman
2003-10-16 20:15 ` Jan Hudec
2003-10-16 20:32 ` Matt Zimmerman
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=3387.1065488945@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=hugh@mimosa.com \
--cc=jdike@addtoit.com \
--cc=mdz@debian.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