On Fri, Mar 25, 2016 at 6:49 PM, Chris Mason <c...@fb.com> wrote: > On Mon, Mar 21, 2016 at 05:52:44PM +0000, Filipe Manana wrote: >> On Mon, Mar 21, 2016 at 5:51 PM, Chris Mason <c...@fb.com> wrote: >> > On Mon, Mar 21, 2016 at 05:38:44PM +0000, fdman...@kernel.org wrote: >> >> From: Filipe Manana <fdman...@suse.com> >> >> >> >> If the lower or upper directory of an overlayfs mount belong to a btrfs >> >> file system and we fsync the file through the overlayfs' merged directory >> >> we ended up accessing an inode that didn't belong to btrfs as if it were >> >> a btrfs inode at btrfs_sync_file() resulting in a crash like the >> >> following: >> > >> > Thanks Filipe, I'll put this in a second pull this week, even if its the >> > only patch in it ;) >> >> Well we need to wait for Miklos patch to be merged first. > > I'll cut this one on top of rc1 in a dedicated branch instead. That way > people can still use the rest of our btrfs pull against v4.5
At the moment, the patch it depends on it's not yet on Linus' tree. But it's in Miklos vfs tree: https://git.kernel.org/cgit/linux/kernel/git/mszeredi/vfs.git/log/?h=overlayfs-next > > -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
