truss and KSE

2002-11-14 Thread Tim Robbins
While experimenting with the new libpthread, I found that if you run
`truss' on a KSE process, both truss and its victim get into a weird
state and don't respond to TERM, INT or QUIT signals. The truss proc
dies if you send it the KILL signal, but the victim process cannot be
killed. Stranger still, it's in the run state but not actually
performing any work.

I understand that KSE is still an experimental feature but I thought
this was worth pointing out because it could be used as a local DoS
and we are nearing 5.0-RELEASE.


Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: truss and KSE

2002-11-14 Thread David Xu
What is your revision of kern_thread.c? revision 1.58 should fix this problem.

- Original Message - 
From: Tim Robbins [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 14, 2002 9:06 PM
Subject: truss and KSE


 While experimenting with the new libpthread, I found that if you run
 `truss' on a KSE process, both truss and its victim get into a weird
 state and don't respond to TERM, INT or QUIT signals. The truss proc
 dies if you send it the KILL signal, but the victim process cannot be
 killed. Stranger still, it's in the run state but not actually
 performing any work.
 
 I understand that KSE is still an experimental feature but I thought
 this was worth pointing out because it could be used as a local DoS
 and we are nearing 5.0-RELEASE.
 
 
 Tim
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: truss and KSE

2002-11-14 Thread Tim Robbins
On Thu, Nov 14, 2002 at 05:39:12AM -0800, David Xu wrote:

 What is your revision of kern_thread.c? revision 1.58 should fix this problem.

I believe it was 1.57. I'll try with 1.58 and let you know if the problem
is still there.


Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message