Care to take a wager that it will be fixed in 4.9.1?
You'd lose that wager. The bug was fixed in the trunk before Linus even reported it but the fix didn't make it into 4.9.1.
For those who didn't bother reading through the LKML discussion and GCC bug reports: GCC 4.5.0 started doing bad things when a certain combination of flags was set, causing it to potentially use the stack pointer red zone even if explicitly told not to. This usually didn't lead to problems because the most programs can afford not to care about whether the red zone is used. The kernel can't; if you use the red zone in the wrong place your system crashes. This was only noticed in 4.9.0 because that version changed around some unrelated code which now caused the kernel to be compiled in such a way that the bug became relevant.
All seems condemned in the long run to approximate a state akin to Gaussian noise. -- James Martin