On Mon, Mar 21, 2016 at 02:08:00PM -0400, Chris Mason wrote: > On Mon, Mar 21, 2016 at 06:58:08PM +0100, David Sterba wrote: > > On Mon, Mar 21, 2016 at 01:51:07PM -0400, Chris Mason wrote: > > > On Mon, Mar 21, 2016 at 05:38:44PM +0000, fdmanana@xxxxxxxxxx wrote: > > > > From: Filipe Manana <fdmanana@xxxxxxxx> > > > > > > > > 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 ;) > > > > I can send you more that I consider relevant for 4.6, low-risk subset of > > what's in the misc-4.6 branch. > > You had sent the list last week, I was going to start with that and look > on the list for anything else urgent. If you have them in a git branch > already I won't say no ;) Meanwhile I had a chance to review and let them through tests so I think it's time for a pull request. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
