Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964985AbWHQNlg (ORCPT ); Thu, 17 Aug 2006 09:41:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964987AbWHQNlb (ORCPT ); Thu, 17 Aug 2006 09:41:31 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:45741 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S964977AbWHQNlN (ORCPT ); Thu, 17 Aug 2006 09:41:13 -0400 Message-ID: <44E471F2.5000003@garzik.org> Date: Thu, 17 Aug 2006 09:41:06 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.5 (X11/20060808) MIME-Version: 1.0 To: Lennart Sorensen CC: Alan Cox , 7eggert@gmx.de, Arjan van de Ven , Dirk , linux-kernel@vger.kernel.org Subject: Re: PATCH/FIX for drivers/cdrom/cdrom.c References: <6Kxns-7AV-13@gated-at.bofh.it> <6Kytd-1g2-31@gated-at.bofh.it> <6KyCQ-1w7-25@gated-at.bofh.it> <1155821951.15195.85.camel@localhost.localdomain> <20060817132309.GX13639@csclub.uwaterloo.ca> In-Reply-To: <20060817132309.GX13639@csclub.uwaterloo.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.3 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 18 Lennart Sorensen wrote: > Why can't O_EXCL mean that the kernel prevents anyone else from issuing > ioctl's to the device? One would think that is the meaning of exlusive. > That way when the burning program opens the device with O_EXCL, no one > else can screw it up while it is open. If it happens to be polled by > hal when the burning program tries to open it, it can just wait and > retry again until it gets it open. Such use of O_EXCL is a weird and non-standard behavior. Jeff - 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/