2009-01-23 Gavin Barraclough <barraclough@apple.com>
authorbarraclough@apple.com <barraclough@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Sat, 24 Jan 2009 03:03:25 +0000 (03:03 +0000)
committerbarraclough@apple.com <barraclough@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Sat, 24 Jan 2009 03:03:25 +0000 (03:03 +0000)
commit686daf3201e8efdbd889761893a07e3c4c72e50d
treec25ecd394d99fd394eae8be68730cee11a07c2c3
parent37898e3d358e63d58d5b77809da32b5de8931fbf
2009-01-23  Gavin Barraclough  <barraclough@apple.com>

        Reviewed by Geoff Garen.

        Fix for <rdar://problem/6126212>
        Ensure that callbacks out from the JSC interface are only allowed
        to return in reverse-chronological order to that in which they were
        made.  If we allow earlier callbacks to return first, then this may
        result in setions of the RegisterFile in use by another thread
        being trampled.

        See uber-comment in JSLock.h for details.

        * runtime/JSLock.cpp:
        (JSC::JSLock::DropAllLocks::DropAllLocks):
        (JSC::JSLock::DropAllLocks::~DropAllLocks):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@40208 268f45cc-cd09-0410-ab3c-d52691b4dbfc
JavaScriptCore/ChangeLog
JavaScriptCore/runtime/JSLock.cpp