Comment 4 for bug 1793901

It seems that this might be only a problem with linux-image-4.15.0-34-generic
I tested it now with linux-image-4.15.0-34-generic and 4.18.0 (self compiled) and in both cases the oops didn't trigger after a reasonable amount of time.
When checking the changelog for -34 it seems there was a change regarding bcache: bcache: fix kcrashes with fio in RAID5 backend dev
Could this be related to that?