linux-kernel - Re: RFC: More functions allowed with O

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

Message-ID: <20150127173045.GA21651@infradead.org>
Date:	Tue, 27 Jan 2015 09:30:45 -0800
From:	Christoph Hellwig <hch@...radead.org>
To:	P??draig Brady <P@...igBrady.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	aneesh.kumar@...ux.vnet.ibm.com,
	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Subject: Re: RFC: More functions allowed with O_PATH

On Tue, Jan 27, 2015 at 12:58:55PM +0000, P??draig Brady wrote:
> Since fsync(), fdatasync(), syncfs() work on an identifying descriptor,
> and all work against a read-only file for example,
> should any/all these functions work with a descriptor opened with O_PATH ?

fsync and fdatasync work on the file data, so they defintively
shouldn't.

syncfs might make sense as we just use it as a handle for the containing
filesystem.

Adding fchmod and fchown would be more useful as they are allowed by
Posix on O_EXEC and O_SEARCH fds.
--
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/