Re: [PATCH] Btrfs: disable xattr operations on subvolume directories

2017-01-25 Thread Omar Sandoval
On Wed, Jan 25, 2017 at 05:06:36PM -0800, Omar Sandoval wrote: > From: Omar Sandoval > > When you snapshot a subvolume containing a subvolume, you get a > placeholder read-only directory where the subvolume would be. These > directory inodes have ->i_ops set to

Re: [PATCH] Btrfs: disable xattr operations on subvolume directories

2017-01-25 Thread Omar Sandoval
On Wed, Jan 25, 2017 at 01:28:21PM +0100, Andreas Gruenbacher wrote: > Omar, > > On Wed, Jan 25, 2017 at 3:38 AM, Omar Sandoval wrote: > > From: Omar Sandoval > > > > When you snapshot a subvolume containing a subvolume, you get a > > placeholder read-only

Re: [PATCH] Btrfs: disable xattr operations on subvolume directories

2017-01-25 Thread Andreas Gruenbacher
Omar, On Wed, Jan 25, 2017 at 3:38 AM, Omar Sandoval wrote: > From: Omar Sandoval > > When you snapshot a subvolume containing a subvolume, you get a > placeholder read-only directory where the subvolume would be. These > directory inodes have ->i_ops set to

Re: [PATCH] Btrfs: disable xattr operations on subvolume directories

2017-01-24 Thread Omar Sandoval
On Tue, Jan 24, 2017 at 06:38:02PM -0800, Omar Sandoval wrote: > From: Omar Sandoval > > When you snapshot a subvolume containing a subvolume, you get a > placeholder read-only directory where the subvolume would be. These > directory inodes have ->i_ops set to

[PATCH] Btrfs: disable xattr operations on subvolume directories

2017-01-24 Thread Omar Sandoval
From: Omar Sandoval When you snapshot a subvolume containing a subvolume, you get a placeholder read-only directory where the subvolume would be. These directory inodes have ->i_ops set to btrfs_dir_ro_inode_operations. Previously, this didn't include the xattr operation