They got support from upstream, and found out that they also needed to upgrade their environment to support the intended madvise semantics. Maybe if they were tracking master, they could have convinced upstream not to call madvise unless proper semantics were available; maybe not.
Sometimes you get lucky and other people find the regressions and the maintenance releases are missing bugs the .0 release had. It's of course nice to check if upstream still has the issue and let them know if so.
At the end of the day, if you need code for your system, you need to be able to maintain it. And this post shows they can.