scsi module starts kernel thread - insmod stays running in 'p s'

[Matt_Domsch en Dell.com]

Per Alan and Manfred, pulling the daemonize() code into it (it's currently a
2.2 module) looks like it will do the trick, as the kernel thread then
"becomes one with init". :)  Yes, it needed to change it's name in
current->comm, and close open file descriptors, but daemonize() should work
nicely.
Thanks to everyone for their help!
-Matt  


-----Original Message-----
From: Matthew Dharm [mailto:mdharm-kernel en one-eyed-alien.net]
Sent: Friday, January 28, 2000 7:42 PM
To: Alan Cox
Cc: Matt_Domsch en exchange.dell.com; linux-kernel en vger.rutgers.edu
Subject: Re: scsi module starts kernel thread - insmod stays running in
'ps'


On Fri, 28 Jan 2000, Alan Cox wrote:

> > Can anyone suggest a reason why the 'insmod driver.o' returns, but is
still
> > running?  Please respond to my email as well, as I read the -digests.
> 
> Vendors driver does a kernel_thread() call in its init ?

If that's the problem, then the driver is also failing to write a
meaninful name into the proper space for display on ps listings.

Matt Dharm

-- 
Matthew Dharm                              Home: mdharm en one-eyed-alien.net 
Engineer, Qualcomm, Inc.                         Work: mdharm en qualcomm.com

I need a computer?
					-- Customer
User Friendly, 2/19/1998

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo en vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/