diff options
author | Martin Pärtel <martin.partel@gmail.com> | 2012-09-14 17:35:58 +0300 |
---|---|---|
committer | Martin Pärtel <martin.partel@gmail.com> | 2012-09-14 17:35:58 +0300 |
commit | 9644b5e1be38a8eddaa70531891cc9da98c93394 (patch) | |
tree | 73c3eb8301bf18cae55114b2929869a72dae4b48 | |
parent | 66e43719bdb58a94240a1e291e3d14e0c0b93826 (diff) | |
download | bindfs-9644b5e1be38a8eddaa70531891cc9da98c93394.tar.gz |
Added a note about a race condition when creating new files.
-rw-r--r-- | src/bindfs.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/bindfs.c b/src/bindfs.c index df0746c..dbbb588 100644 --- a/src/bindfs.c +++ b/src/bindfs.c @@ -290,6 +290,8 @@ static int getattr_common(const char *procpath, struct stat *stbuf) return 0; } +/* FIXME: another thread may race to see the old owner before the chown is done. + Is there a scenario where this compromises security? Or application correctness? */ static void chown_new_file(const char *path, struct fuse_context *fc, int (*chown_func)(const char*, uid_t, gid_t)) { uid_t file_owner; |