You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/07/02 20:03:26 UTC

DO NOT REPLY [Bug 21287] New: - no mutex lock protection in decrement_refcount

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21287>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21287

no mutex lock protection in decrement_refcount

           Summary: no mutex lock protection in decrement_refcount
           Product: Apache httpd-2.0
           Version: 2.0.46
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other Modules
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: m.torquati@huginsoft.it


There are no mutex lock protection in decrement_refcount if it is
defined USE_ATOMICS.

I think you simply forgot the mutex in function decrement_refcount. 
There is a race condition in the cleanup_cache_object when two threads 
are trying to clean-up the same object which is no longer referenced in the cache.
I found this problem while looking for the bug 21285. The proposed patch
fix the problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org