From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Chris Wedgwood <cw@f00f.org>
Cc: Jeff Dike <jdike@addtoit.com>,
Blaisorblade <blaisorblade_spam@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [uml-devel] Re: [PATCH] UML: Use PTRACE_KILL instead of SIGKILL to kill host-OS processes
Date: Wed, 03 Nov 2004 11:47:38 +0000 [thread overview]
Message-ID: <1099482457.16445.1.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <20041103113736.GA23041@taniwha.stupidest.org>
On Wed, 2004-11-03 at 11:37, Chris Wedgwood wrote:
> kill(..., SIGKILL) doesn't work to kill host-OS processes created in
> the exec path in TT mode --- for this we need PTRACE_KILL (it did work
> in previous kernels, but not by design). Without this process will
> accumulate on the host-OS (although the won't be visible inside UML).
>
> Signed-off-by: Chris Wedgwood <cw@f00f.org>
> ---
>
> Yes, there are other fixes along these lines which are needed but one
> at a time as we test these...
>
> Index: cw-current/arch/um/kernel/tt/exec_user.c
> ===================================================================
> --- cw-current.orig/arch/um/kernel/tt/exec_user.c 2004-11-03 02:10:18.064830204 -0800
> +++ cw-current/arch/um/kernel/tt/exec_user.c 2004-11-03 02:12:10.447716745 -0800
> @@ -35,7 +35,8 @@
> tracer_panic("do_exec failed to get registers - errno = %d",
> errno);
>
> - kill(old_pid, SIGKILL);
> + if (ptrace(PTRACE_KILL, old_pid, NULL, NULL))
> + printk("Warning: ptrace(PTRACE_KILL, %d, ...) saw %d\n", errno);
You have two %d but only one argument. You seem to have forgotten an
"old_pid, " in there.
>
> if(ptrace_setregs(new_pid, regs) < 0)
> tracer_panic("do_exec failed to start new proc - errno = %d",
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/, http://www-stu.christs.cam.ac.uk/~aia21/
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
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-11-03 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 11:37 [uml-devel] [PATCH] UML: Use PTRACE_KILL instead of SIGKILL to kill host-OS processes Chris Wedgwood
2004-11-03 11:47 ` Anton Altaparmakov [this message]
2004-11-03 12:08 ` [uml-devel] [PATCH] UML: Use PTRACE_KILL instead of SIGKILL to kill host-OS processes (take #2) Chris Wedgwood
2004-11-03 19:28 ` Blaisorblade
2004-11-03 20:09 ` Chris Wedgwood
2004-11-03 22:51 ` Blaisorblade
2004-11-03 20:18 ` Gerd Knorr
2004-11-03 20:48 ` Chris Wedgwood
2004-11-04 0:23 ` Blaisorblade
2004-11-03 23:19 ` Blaisorblade
2004-11-19 16:17 ` [uml-devel] [PATCH] UML: Use PTRACE_KILL instead of SIGKILL to kill host-OS processes Bodo Stroesser
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=1099482457.16445.1.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=cw@f00f.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.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