Date: Fri, 31 Jul 1998 15:16:36 -0400 From: "Brian J. McGovern" <mcgovern@spoon.beta.com> To: Open Systems Networking <opsys@mail.webspan.net> Cc: hackers@FreeBSD.ORG Subject: Re: O_SHLOCK and O_EXLOCK during open... (locking for devices?) Message-ID: <199807311916.PAA14142@spoon.beta.com> In-Reply-To: Your message of "Fri, 31 Jul 1998 14:55:19 EDT." <Pine.BSF.3.95.980731145432.7771A-100000@orion.webspan.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the feedback... uu_lock and family is possible to use, but it will fail with applications that don't check or use the facility ( a lot of poorly written ones). I need something thats more kernel-oriented, that will catch a lock issue during the open() call. I'd even make the changes in the driver(s), if required, but it appears the error is caused outside of the driver open() call, and therefore I really can't hook in to it until its too late. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807311916.PAA14142>