[Mod-security-developers] [JIRA] Resolved: (MODSEC-173) under high load (depending on IO speed), auditlog could loose entries due to race condition in apr_dir_make_recursive()

[Breno S. P. (JIRA) <no...@mo...>]

     [ https://www.modsecurity.org/tracker/browse/MODSEC-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Breno Silva Pinto resolved MODSEC-173.
--------------------------------------

    Resolution: Fixed

> under high load (depending on IO speed), auditlog could loose entries due to race condition in apr_dir_make_recursive()
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MODSEC-173
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-173
>             Project: ModSecurity
>          Issue Type: Bug
>      Security Level: Normal
>          Components: Logging
>    Affects Versions: 2.5.12
>         Environment: using libapr-1.so.0.4.2 from apache httpd 2.2.16
>            Reporter: Christoph Moench-Tegeder
>            Assignee: Breno Silva Pinto
>             Fix For: 2.6.0
>
>         Attachments: msc_logging.c.diff
>
>
> When running multiple threads with apache, several audit log entries might be written at (more or less) exactly the same time. In this case apr_dir_make_recursive() can return APR_EEXIST (classical stat()/mkdir() race condition). In this case, writing the audit log entry will fail with the message "Failed to create subdirectories: File exists".
> To work around this issue, one should allow APR_EEXIST from apr_dir_make_recursive(), too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://www.modsecurity.org/tracker/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira