Change Details

This was supposed to be fixed in {T125177}. But when F4932228 was rebased to be applied as {4d38a489}, part of the code was incorrectly rebased after changes in {47e2bec3}, causing it to not actually function properly. When reviewing an unrelated patch I noticed a bit of code that made no sense, and tracked it down to the above situation.

This was supposed to be fixed in {T125177}. But when F4932228 was rebased to be applied as {4d38a489}, part of the code was incorrectly rebased after changes in {47e2bec3}, causing it to not actually function properly. When reviewing an unrelated patch I noticed a bit of code that made no sense, and tracked it down to the above situation. This was CVE-2017-0361 on the last release (will reuse for reference)

This was supposed to be fixed in {T125177}. But when F4932228 was rebased to be applied as {4d38a489}, part of the code was incorrectly rebased after changes in {47e2bec3}, causing it to not actually function properly. When reviewing an unrelated patch I noticed a bit of code that made no sense, and tracked it down to the above situation. This was CVE-2017-0361 on the last release (will reuse for reference)