> No, it has nothing to do with calling mem<foo> in a signal handler.
Sure it does. If the signal handler call was compiled with the new GCC, then it will expect
the flag to be clear on entry. If the flag happens to be set and the signal handler calls
mem<foo>, the copy will go backward. This can be exploited.