From: "Richard W.M. Jones" <rjones@redhat.com>
To: Richard Weinberger <richard@nod.at>
Cc: "user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] How to reliably kill all vmlinux processes for a single VM?
Date: Tue, 13 Aug 2013 13:25:33 +0100 [thread overview]
Message-ID: <20130813122533.GF10864@redhat.com> (raw)
In-Reply-To: <20130813120401.GE10864@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Tue, Aug 13, 2013 at 01:04:01PM +0100, Richard W.M. Jones wrote:
> OK, I understand what's going wrong and how to reproduce the
> signal-to-parent problem. It does look like a bug in vmlinux.
>
> It happens if the init process (PID 1) inside the VM gets a segfault.
To add an additional data-point, applying the attached patch causes
the rogue SIGTERM-to-parent signal to disappear. So at least we know
where it comes from!
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
[-- Attachment #2: 0001-COMMENT-OUT-KILL-SIGTERM.patch --]
[-- Type: text/plain, Size: 700 bytes --]
>>From 73e2153039803d6f8cec7425ae501f857d9523a9 Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Tue, 13 Aug 2013 13:24:32 +0100
Subject: [PATCH] COMMENT OUT KILL SIGTERM
---
arch/um/os-Linux/util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/um/os-Linux/util.c b/arch/um/os-Linux/util.c
index 492ef5e..a0f308e 100644
--- a/arch/um/os-Linux/util.c
+++ b/arch/um/os-Linux/util.c
@@ -108,7 +108,7 @@ void os_dump_core(void)
*/
signal(SIGTERM, SIG_IGN);
- kill(0, SIGTERM);
+ //kill(0, SIGTERM);
/*
* Most of the other processes associated with this UML are
* likely sTopped, so give them a SIGCONT so they see the
--
1.8.3.1
[-- Attachment #3: Type: text/plain, Size: 405 bytes --]
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
[-- Attachment #4: Type: text/plain, Size: 194 bytes --]
_______________________________________________
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:[~2013-08-13 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 17:48 [uml-devel] How to reliably kill all vmlinux processes for a single VM? Richard W.M. Jones
2013-08-12 7:37 ` richard -rw- weinberger
2013-08-12 8:15 ` richard -rw- weinberger
2013-08-12 8:53 ` Richard W.M. Jones
2013-08-13 10:36 ` Richard W.M. Jones
2013-08-13 10:49 ` Richard Weinberger
2013-08-13 11:06 ` Richard W.M. Jones
2013-08-13 12:04 ` Richard W.M. Jones
2013-08-13 12:25 ` Richard W.M. Jones [this message]
2013-08-15 17:34 ` richard -rw- weinberger
2013-08-15 18:01 ` Richard W.M. Jones
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=20130813122533.GF10864@redhat.com \
--to=rjones@redhat.com \
--cc=richard@nod.at \
--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