Hi Ross,
Thanks for the report. I have analyzed it here [1] earlier and is
harmless since lockdep checks doesn't seem to account for the
difference in the lock time-space, there is similar fix in block
layer as well (which I am unable to pull the ref as of now, but
will try again). And thi
I was testing my new xfstest posted here:
https://lists.01.org/pipermail/linux-nvdimm/2018-July/016850.html
against a btrfs test device + scrach device setup, and hit a lockdep
splat. I'm using vanilla v4.18.6.
I've attached the splats to this mail, one just as it happened in
dmesg and one pass
