I've seen it a few times.
> Things like nfsd are always holding the BKL, only
> releasing it on schedule(), and exit. Is there any compelling reason to
> hold the BKL during times other than during the daemonize() process?
In general there is no reason. If the data the thread accesses is not
protected by anything but BKL it must hold it - else it seems superflous
to me.
Christoph
-- Of course it doesn't work. We've performed a software upgrade. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/