| |||||||||||||
|
| |||||||||||||
Linux 2.6.30 exploit postedLinux 2.6.30 exploit postedPosted Jul 17, 2009 14:28 UTC (Fri) by Trou.fr (subscriber, #26289)In reply to: Linux 2.6.30 exploit posted by trasz Parent article: Linux 2.6.30 exploit posted
because if the check had not been optimized away, you wouldn't have been able to pass it to exploit the vulnerability.
(Log in to post comments)
Linux 2.6.30 exploit posted Posted Jul 17, 2009 20:43 UTC (Fri) by stevenb (guest, #11536) [Link]
Then the author of the code should have made the pointer volatile, or he/she should protect it with a lock. The optimization that GCC did, appears to be valid (but IANALL).
|
|
||||||||||||