Comment 209 for bug 1470250

I've also been running dfbdac2e for 48 hours without hitting the bug.

I don't think bad commit is in the hv_storvsc driver or any HV specific code. I'm not sure how to explain that yet. I tested a kernel with all the HV related commits(c8c38b3, 7af024a and 6ad4874) reverted and the bug still happened.

The current test results indicate the bad commit is somewhere in between dfbdac2 and 5e6cf71 or maybe 83215219 per comment #204.

There are two HV commit in that range is:
7af024a hv: use correct order when freeing monitor_pages
Drivers: hv: balloon: Ensure pressure reports are posted regularly

However, reverting those commits have already been tested as bad.

There are three ext4 commits in that range, which may be related:
265dabe ext4: fix wrong assert in ext4_mb_normalize_request()
d4d2e7e ext4: fix zeroing of page during writeback
cd4842f4 ext4: fix data integrity sync in ordered mode

@faulpeltz, I'm going to mark commit dfbdac2e as good and start on the next kernel. Can you test 5e6cf71 and/or 83215219 to confirm they are bad.