Remove unsafe uses of AtomicallyInitializedStatic
authorandersca@apple.com <andersca@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Sun, 12 Jan 2014 17:33:38 +0000 (17:33 +0000)
committerandersca@apple.com <andersca@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Sun, 12 Jan 2014 17:33:38 +0000 (17:33 +0000)
commit5ccc1a333aedf11721c936ad9d179c1bec3ae061
tree5c0524546fa5a1b2ca141a17b6b4ba66e9c3f390
parent2009259befd08ca4bc924b2657aa131cc78ce985
Remove unsafe uses of AtomicallyInitializedStatic
https://bugs.webkit.org/show_bug.cgi?id=126838

Reviewed by Andreas Kling.

AtomicStrings are per thread so any static initialization of them is potentially dangerous
unless it's certain that they're only ever used from the same thread.

This goes against using them with AtomicallyInitializedStatic, so just create AtomicStrings where needed.
(This is highly unlikely to have any real negative performance impact since these two functions
aren't called very frequently).

* loader/CrossOriginAccessControl.cpp:
(WebCore::passesAccessControlCheck):
* page/PerformanceResourceTiming.cpp:
(WebCore::passesTimingAllowCheck):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@161812 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/loader/CrossOriginAccessControl.cpp
Source/WebCore/page/PerformanceResourceTiming.cpp