Re: [PATCH 1/2] Btrfs: fix permissions of empty files not affected by umask

On Thu, Nov 29, 2012 at 07:40:08PM -0800, Filipe Brandenburger wrote: > 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

[PATCH 1/2] 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

[PATCH 1/2] 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

Re: [PATCH 1/2] Btrfs: fix permissions of empty files not affected by umask

On Thu, Nov 29, 2012 at 07:40:08PM -0800, Filipe Brandenburger wrote: 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