Hello,
With,
commit 59724793983177d1b51c8cdd0134326977a1cabc
Author: Christoph Hellwig <hch@xxxxxx>
Date: Thu Apr 27 09:42:25 2017 +0200
fs: completely ignore unknown open flags
[ Upstream commit 629e014bb8349fcf7c1e4df19a842652ece1c945 ]
Currently we just stash anything we got into file->f_flags, and the
report it in fcntl(F_GETFD). This patch just clears out all unknown
flags so that we don't pass them to the fs or report them.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Sasha Levin <alexander.levin@xxxxxxxxxxx>
and,
commit 666d1fc2023eee3bf723c764eeeabb21d71a11f2
Author: Christoph Hellwig <hch@xxxxxx>
Date: Thu Apr 27 09:42:24 2017 +0200
fs: add a VALID_OPEN_FLAGS
[ Upstream commit 80f18379a7c350c011d30332658aa15fe49a8fa5 ]
Add a central define for all valid open flags, and use it in the uniqueness
check.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Sasha Levin <alexander.levin@xxxxxxxxxxx>
The kernel prevents unknown open flags from being passed through to the
underlying filesystem. I am wondering if people would be for or against the
idea of provisioning some number of bits in the open flags that are opaque to
the VFS layer but get passed down to the underlying filesystem? The motivation
would be to allow filesystem specific semantics to be controllable via open,
much like the more generic and pre-existing open flags.
Thanks,
Rodney Fu
