O_CAREFUL flag to disable open() side effects

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alan Cox wrote:
Ar Iau, 2006-07-27 am 20:05 +0300, ysgrifennodd Pekka J Enberg:
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.

Dumb thought: would it make sense to add an O_CAREFUL flag to open(), to disable side effects? It seems that a number of devices have this issue and one have to jump through weird hoops to configure them. Obviously, a file descriptor obtained with O_CAREFUL may not be fully functional, at the device driver's option.

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.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux