linux-kernel - Re: O_CAREFUL flag to disable open() side effects

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1154023516.13509.72.camel@localhost.localdomain>
Date:	Thu, 27 Jul 2006 19:05:16 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Pekka J Enberg <penberg@...Helsinki.FI>,
	Ulrich Drepper <drepper@...il.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...l.org, viro@...iv.linux.org.uk, tytso@....edu,
	tigran@...itas.com
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/