diff options
author | 2012-11-30 03:40:08 +0000 | |
---|---|---|
committer | 2012-12-16 20:46:28 -0500 | |
commit | 9185aa587b7425f8f4520da2e66792f5f3c2b815 (patch) | |
tree | 33ec92228186bbb37215a7e8db2c2a4519b102ad /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Btrfs: put raid properties into global table (diff) | |
download | linux-dev-9185aa587b7425f8f4520da2e66792f5f3c2b815.tar.xz linux-dev-9185aa587b7425f8f4520da2e66792f5f3c2b815.zip |
Btrfs: fix permissions of empty files not affected by umask
When a new file is created with btrfs_create(), the inode will initially be
created with permissions 0666 and later on in btrfs_init_acl() it will be
adapted to mask out the umask bits. The problem is that this change won't make
it into the btrfs_inode unless there's another change to the inode (e.g. writing
content changing the size or touching the file changing the mtime.)
This fix adds a call to btrfs_update_inode() to btrfs_create() to make sure that
the change will not get lost if the in-memory inode is flushed before other
changes are made to the file.
Signed-off-by: Filipe Brandenburger <filbranden@google.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions