From owner-freebsd-hackers Thu Aug 6 16:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01074 for freebsd-hackers-outgoing; Thu, 6 Aug 1998 16:17:22 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01042 for ; Thu, 6 Aug 1998 16:17:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-129.camalott.com [208.229.74.129]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA19775; Thu, 6 Aug 1998 18:17:59 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA01215; Thu, 6 Aug 1998 18:16:37 -0500 (CDT) (envelope-from joelh) Date: Thu, 6 Aug 1998 18:16:37 -0500 (CDT) Message-Id: <199808062316.SAA01215@detlev.UUCP> To: mcgovern@spoon.beta.com CC: n@nectar.com, mcgovern@spoon.beta.com, hackers@FreeBSD.ORG In-reply-to: <199808061159.HAA01248@spoon.beta.com> (mcgovern@spoon.beta.com) Subject: Re: O_SHLOCK and O_EXLOCK - change to layering required? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808061159.HAA01248@spoon.beta.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yeah, but 80% of my problem is the fact they cause the open() call > on a device to fail with varying error codes, depending on the type > of device. On my own device, it appears that the error condition > occurs even before the driver open() call gets called. Oh, I see. I thought that it would return EOPNOTSUPP for all cases. > I think locking would be far more useful if locking would be passed > down through the layers until either a layer that COULD handle it > became involved, or the DRIVER said "Nope, not supported here", or > even silently ignored the lock request. Ugh. Don't silently ignore lock requests. Then you get corruption and don't know why. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message