lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 01 Feb 2009 14:37:03 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	George Kumar <grgkumar4@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Killing a kernel thread from user space ?

George Kumar wrote:
> Hi,
> 
> Is it possible to kill a kernel thread from user space. Don't ask me
> why do I need to do this. This is purely an experimental exercise, I
> am not doing it because I am working on a practical problem. Thing is
> that I wrote a kernel module and now it is hung in a kernel thread
> somewhere doing udelay(), fortunately since I am on preemptible kernel
>  my machine is not frozen,
> but still I saw that doing a kill -9 on this process has no effect.
> How about if I insert another kernel module and kill this busywait
> thread from inside the kernel space. In effect how do you execute
> "kill -9" from one kernel thread to misbehaving kernel thread.

You can't, really. Kernel threads (or any kernel code) can't be 
interrupted by signals, except where they are explicitly coded so that 
they can be (breaking out of a loop due to signal_pending(), etc.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ