On Fri, Dec 23, 2016 at 04:18:00PM -0800, Liu Bo wrote: > > > Btw, I was able to reproduce the issue on kdave/for-next branch with "Merge > > > branch 'for-next-next-4.9-20161125' into for-next-20161125" as the topmost > > > commit. The issue cannot be reproduced yet on latest code available from > > > kdave/for-next branch. > > > > Maybe changes in upstream might have masked the issue in the recent > > kdave/for-next branch. I say that because 'git bisect' resulted in the > > following commit ... > > I guess that the for-next branch didn't revert this patch[1] as upstream > did, [...] > [1]: Btrfs: adjust len of writes if following a preallocated extent > https://patchwork.kernel.org/patch/9413129/ The revert was present in the for-next-20161219 branch, the for-next branches sit on top of recent upstream rc tag and are merged from various dev branches so the patch difference should be minimal in the end. -- 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
