I reviewed the btrfs commits in v4.18-rc1, but the are quite a few of them. We should perform a "Reverse" bisect to identify the correct on that fixes this bug.
I started a "Reverse" bisect between v4.17 final and v4.18-rc1.
I built the first test kernel, up to the following commit:
1c8c5a9d38f607c0b6fd12c91cbe1a4418762a21
I reviewed the btrfs commits in v4.18-rc1, but the are quite a few of them. We should perform a "Reverse" bisect to identify the correct on that fixes this bug.
I started a "Reverse" bisect between v4.17 final and v4.18-rc1.
I built the first test kernel, up to the following commit: 0b6fd12c91cbe1a 4418762a21
1c8c5a9d38f607c
The test kernel can be downloaded from: kernel. ubuntu. com/~jsalisbury /lp1752961
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance