Alex Hornung <ahornung@gmail.com> added the comment:
The alias issue looks good now.=20
I've noticed something else though: in the path from devfs_unlinkp or any=20
other for that matter, you call hotplug_devfs_* and from there=20
hotplug_put_event, which in turn acquires a lockmgr lock, meaning it can go=
to=20
sleep. I don't think this is a good idea, as all devfs functions you are=20
hooking hold the devfs_lock. You could put a process to sleep that is holdi=
ng=20
a different lock.=20
I'm not sure how much of an issue this can be or how to best approach it. F=
or=20
notifications as these, lwkt messages come to my mind, but there might be=20
another solution, or it might not even be that bad.
If anyone else can provide some insight on how to approach this, it would b=
e=20
good.
Cheers,
Alex Hornung
_____________________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1616>
_____________________________________________________