Re: O_CAREFUL flag to disable open() side effects

Ar Iau, 2006-07-27 am 10:33 -0700, ysgrifennodd H. Peter Anvin:
> For a conventional file, directory, or block device O_CAREFUL is a 
> no-op.  For ttys it would typically behave similar to O_NONBLOCK 
> followed immediately by a fcntl to clear the nonblock flag.

Linus long ago suggested O_NONE to go with RO/RW/WO. Its not that hard
to do with the current file op stuff but you have to work out what the
access permission semantics of it are and what it means for ioctl etc

-
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: O_CAREFUL flag to disable open() side effects
    • From: "H. Peter Anvin" <[email protected]>

• References:
  • [RFC/PATCH] revoke/frevoke system calls V2
    • From: Pekka J Enberg <[email protected]>
  • Re: [RFC/PATCH] revoke/frevoke system calls V2
    • From: "Ulrich Drepper" <[email protected]>
  • Re: [RFC/PATCH] revoke/frevoke system calls V2
    • From: Pekka J Enberg <[email protected]>
  • Re: [RFC/PATCH] revoke/frevoke system calls V2
    • From: Alan Cox <[email protected]>
  • O_CAREFUL flag to disable open() side effects
    • From: "H. Peter Anvin" <[email protected]>

• Prev by Date: Re: [RFC/PATCH] revoke/frevoke system calls V2
• Next by Date: Re: [patch] Reorganize the cpufreq cpu hotplug locking to not be totally bizare
• Previous by thread: Re: O_CAREFUL flag to disable open() side effects
• Next by thread: Re: O_CAREFUL flag to disable open() side effects
• 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]