On Tue, Aug 05, 2014 at 09:52:46AM -0400, Chris Mason wrote: > On 08/05/2014 09:47 AM, Chris Mason wrote: > > On 08/04/2014 09:57 PM, Dave Jones wrote: > >> On Mon, Aug 04, 2014 at 09:28:45PM -0400, Dave Jones wrote: > >> > Possibly related to some changes I've been making to my fuzz tester > >> today > >> > to operate on the same file from multiple threads. > >> > This was on v3.16-829-g98959948a7ba, but probably exists on earlier > >> trees too > >> > given the lack of btrfs specific commits so far this merge window. > >> > >> reproducer: > >> > >> trinity -q -l off -c lseek -c write > >> > >> (Things also go very, very bad if you then try to umount that > >> partition - endless oopses, too mangled to parse). > > > > So we're fuzzing lseek and btrfs goes crazy? Looking. > > Ugh, that's wrong in exciting ways. Thanks Dave, I'll test a patch with > trinity and get it in.
You'll need the latest tree from git to hit this btw. https://github.com/kernelslacker/trinity Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
