All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
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 11:36:03 +0100	[thread overview]
Message-ID: <20130813103603.GA27173@redhat.com> (raw)
In-Reply-To: <20130812085300.GV5918@redhat.com>

On Mon, Aug 12, 2013 at 09:53:00AM +0100, Richard W.M. Jones wrote:
> On Mon, Aug 12, 2013 at 10:15:24AM +0200, richard -rw- weinberger wrote:
> > Found the root cause, patch is on the way.
> 
> I can test patches if you CC me on them.

I'm still available to test patches :-)  Didn't see anything on
this list nor on LKML.

In particular I'm having a problem where it looks as if vmlinux is
sending a signal to its parent process on shutdown.

I can reliably reproduce this, although not with anything very
minimal.  But if you run the libguestfs test suite like this you'll
see it:

  make -C tests/regressions check TESTS=rhbz914931

The parent process (a C program which for unrelated reasons is called
'rhbz914931') receives a SIGTERM.  I checked the siginfo struct for
this signal, and it appears to come from the vmlinux main process,
which should not be happening.

So .. possibly there's something awry with how vmlinux delivers
signals to its child processes on shutdown which is causing it both to
miss out some children, and to kill other unrelated processes.  Or
maybe this is just a coincidence.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)

------------------------------------------------------------------------------
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
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


  reply	other threads:[~2013-08-13 10:36 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 [this message]
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
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=20130813103603.GA27173@redhat.com \
    --to=rjones@redhat.com \
    --cc=richard.weinberger@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.