Re: [RFC/PATCH] revoke/frevoke system calls V2

Hi!

> > Sure. Though I wonder if sys_frevoke is enough for us and we can drop 
> > sys_revoke completely.
> 
> Alas not. Some Unix devices have side effects when you open() them. 

We probably want some other solution for those, anyway...? Like
open(..., O_NONE)?
							Pavel
-- 
Thanks for all the (sleeping) penguins.
-
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]>

Prev by Date: Re: [PATCH] [MMC] Fix base address configuration in wbsd
Next by Date: Re: use persistent allocation for cursor blinking.
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]