Re: O_CAREFUL flag to disable open() side effects

On 7/27/06, H. Peter Anvin <[email protected]> wrote:

Dumb thought: would it make sense to add an O_CAREFUL flag to open(), to
disable side effects?


Not that I don't want to be constructive, but this is something you'll
likely never be able to specify with the needed level of accuray.
What is careful?  I can imagine all kinds ideas possible ways file
systems and device drivers might want to use this.

Adding a separate interface taking a file name isn't high enough a
price to open such a can of worms.
-
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/

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: Require mmap handler for a.out executables
Next by Date: Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion
Previous by thread: Re: O_CAREFUL flag to disable open() side effects
Next by thread: Re: [RFC/PATCH] revoke/frevoke system calls V2
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]