Re: Right way to start a lightweight kernel thread without copying open file descriptors?

[Gregory Nutt]

in my case the device driver keeps track whether the kernel thread runs and
> returns EBUSY If thats the case for a second start attempt. Would that be
> sufficient to avoid the security risk you are considering?
>
>
Yes.  A more typical use case would be to start the kernel thread at the
time that the driver is initialized.