mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	7eggert@gmx.de, Dirk <noisyb@gmx.net>,
	linux-kernel@vger.kernel.org
Subject: Re: PATCH/FIX for drivers/cdrom/cdrom.c
Date: Thu, 17 Aug 2006 16:38:41 +0200	[thread overview]
Message-ID: <1155825521.4494.68.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060817143633.GF13641@csclub.uwaterloo.ca>

On Thu, 2006-08-17 at 10:36 -0400, Lennart Sorensen wrote:
> On Thu, Aug 17, 2006 at 02:48:50PM +0100, Alan Cox wrote:
> > Ar Iau, 2006-08-17 am 09:23 -0400, ysgrifennodd Lennart Sorensen:
> > > 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.
> > 
> > If you were designing a new OS from scratch you might want to explore
> > that semantic as a design idea. I wouldn't recommend it because a lot of
> > apps will be upset if they issue an ioctl and it mysteriously fails or
> > hangs.
> 
> I think hal should get an error when it tries to open the cdrom device
> when the burning application is using it. 

this is what O_EXCL is for ;)


> Hmm, so how does one tell hal to go to hell and leave the cdrom device
> alone at all times (other than totally disabling hal). 

make sure hal uses O_EXCL, and if not, beat up the hal guys about it ;)

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com


  reply	other threads:[~2006-08-17 14:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6Kxns-7AV-13@gated-at.bofh.it>
     [not found] ` <6Kytd-1g2-31@gated-at.bofh.it>
     [not found]   ` <6KyCQ-1w7-25@gated-at.bofh.it>
2006-08-17 12:27     ` Bodo Eggert
2006-08-17 12:35       ` Arjan van de Ven
2006-08-18 12:31         ` Bodo Eggert
2006-08-18 12:53           ` Arjan van de Ven
2006-08-18 16:45           ` Alan Cox
2006-08-17 13:39       ` Alan Cox
2006-08-17 13:23         ` Lennart Sorensen
2006-08-17 13:41           ` Jeff Garzik
2006-08-17 13:54             ` Lennart Sorensen
2006-08-17 14:38               ` Helge Hafting
2006-08-18 12:39                 ` Bodo Eggert
2006-08-17 13:48           ` Alan Cox
2006-08-17 14:36             ` Lennart Sorensen
2006-08-17 14:38               ` Arjan van de Ven [this message]
2006-08-17 15:09               ` Alan Cox
2006-08-19 17:52               ` Oleg Verych
2006-08-21 17:31                 ` Lennart Sorensen
2006-08-16 17:26 Dirk
2006-08-16 17:40 ` Jan Engelhardt
2006-08-16 18:37   ` Dirk
2006-08-16 18:37 ` Lennart Sorensen
2006-08-16 18:44   ` Arjan van de Ven
2006-08-16 19:30   ` Dirk
2006-08-16 19:08 ` Alan Cox
2006-08-16 22:25 ` Andrew Morton
2006-08-17  7:50   ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1155825521.4494.68.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=7eggert@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=noisyb@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®