Re: PATCH/FIX for drivers/cdrom/cdrom.c

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: PATCH/FIX for drivers/cdrom/cdrom.c
    • From: Lennart Sorensen <[email protected]>

• References:
  • Re: PATCH/FIX for drivers/cdrom/cdrom.c
    • From: Bodo Eggert <[email protected]>
  • Re: PATCH/FIX for drivers/cdrom/cdrom.c
    • From: Alan Cox <[email protected]>
  • Re: PATCH/FIX for drivers/cdrom/cdrom.c
    • From: Lennart Sorensen <[email protected]>

• Prev by Date: Re: [RFC][PATCH 7/7] UBC: proc interface
• Next by Date: [RFC][PATCH 54/75] net: net/rrunner.c pci_module_init to pci_register_driver conversion
• Previous by thread: Re: PATCH/FIX for drivers/cdrom/cdrom.c
• Next by thread: Re: PATCH/FIX for drivers/cdrom/cdrom.c
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]