Re: vgone() calling VOP_CLOSE() -> blocked threads?

From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
Date: Sat, 15 Mar 2008 19:48:04 +0000

To be honest, I'm not completely sure how to solve this issue, though I
know it should at least do something similar to this:

- The device driver should have a seperate routine (d_revoke) to wake
up any blocked threads, to make sure they leave the device driver
properly.

It's already there, it's called d_purge().

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

References:
- vgone() calling VOP_CLOSE() -> blocked threads?
  - From: Ed Schouten

Prev by Date: Re: [PATCH] hwpmc(4) changes to use 'mp_maxid' instead of 'mp_ncpus'.
Next by Date: Re: vgone() calling VOP_CLOSE() -> blocked threads?
Previous by thread: Re: vgone() calling VOP_CLOSE() -> blocked threads?
Next by thread: Some devfs and tty issues
Index(es):
- Date
- Thread