linux-kernel - O_TMPFILE detection

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-next>] [day] [month] [year] [list]

Message-ID: <20140211160302.GA18936@infradead.org>
Date:	Tue, 11 Feb 2014 08:03:02 -0800
From:	Christoph Hellwig <hch@...radead.org>
To:	Alexander Viro <viro@...iv.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-man@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: O_TMPFILE detection

I've started implementing support for O_TMPFILE in xfs_io in preparation
for proper testcases and found something rather annoying:

Given that we implicitly pass O_DIRECTORY as part of the full O_TMPFILE
flag an open using O_TMPFILE will simply succeed on a kernel old enough
to not have O_TMPFILE support, and give you a file descriptor for the
directory passed in.  Of course this only works if you open the fd
read-only which isn't all that useful for real temporary files, but it
would be the natural choice for a feature test.

I guess we can't really fix this up any more, but does anyone have a
good idea how to document this properly in the man page?
--
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/