linux-kernel - Re: [RFC] correct flags to f_mode conversion in __dentry

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: <20080317104537.GA32546@infradead.org>
Date:	Mon, 17 Mar 2008 06:45:37 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Alan Cox <alan@...hat.com>
Cc:	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
	aviro@...hat.com, drepper@...hat.com, hch@...radead.org,
	sds@...ho.nsa.gov, jmorris@...ei.org, mtk.manpages@...il.com
Subject: Re: [RFC] correct flags to f_mode conversion in __dentry_open

On Sat, Mar 15, 2008 at 05:59:52PM -0400, Alan Cox wrote:
> > does 11 really mean and should it really always be mapped to (FMODE_READ
> > | FMODE_WRITE) or should it continue to get mapped to 'no permission?'
> 
> We've always mapped 3 to "no permission" to read or write. It's a linuxism

I've tripped over this recently aswell.  It would for sure be useful
to add a sumbolic O_FOO constant for this magic value '3' and document
it in the manpage.
--
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/