| |||||||||||||
Why is this a problem?Why is this a problem?Posted Mar 19, 2008 22:33 UTC (Wed) by klossner (subscriber, #30046)In reply to: Why is this a problem? by vonbrand Parent article: GCC 4.3.0 exposes a kernel bug
> 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.
(Log in to post comments)
|
|||||||||||||