On 2/19/26 9:02 PM, Ivan Sergeev wrote:
On Fri Feb 20, 2026 at 5:38 AM MSK, Ivan Sergeev wrote:
I've done the bisect using the v6.12.68 tag as good and v6.18.8 tag as bad
Sorry, those are not the tags I've used for the bisect. Before doing a
bisect in git I first checked versions from 6.18 to 6.13, and could
reproduce the issue in all of them, so after that I went for the git
bisect between 6.12.68 and 6.13.6.
I'm wondering if you actually have a second regression manifesting
similarly.
Can you check out at your bad commit and apply just 7f2b5237e313 at the
bad commit? Confirm that fixes it.
If it does, then redo your bisect applying 7f2b5237e313 where applicable.
