On Fri, 2018-06-29 at 00:42 +1000, Michael Ellerman wrote: > Kent, Jens, > > This looks like it might be related to the recent bioset changes? > > cheers > > Abdul Haleem <abdhalee@xxxxxxxxxxxxxxxxxx> writes: > > On Tue, 2018-06-26 at 23:36 +1000, Michael Ellerman wrote: > >> Abdul Haleem <abdhalee@xxxxxxxxxxxxxxxxxx> writes: > ... > > I was able to reproduce again with slub_debug=FZP and DEBUG_INFO enabled > > on 4.17.0-rc7-next-20180601, but not much traces other than the Oops stack trace > > Are you still testing on that revision? It's nearly a month old. > > Please try to reproduce on mainline or today's linux-next. Problem is not reproducible on 4.18.0-rc3 mainline and today's next kernel -- Regard's Abdul Haleem IBM Linux Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
