This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/19429] New: syslog unusable after fork from a multi-threaded program


https://sourceware.org/bugzilla/show_bug.cgi?id=19429

            Bug ID: 19429
           Summary: syslog unusable after fork from a multi-threaded
                    program
           Product: glibc
           Version: 2.23
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---
             Flags: security-

syslog uses a lock internally, and the lock is not reset during fork.  This
means that after a fork, syslog can deadlock in the child process.

Technically, this is not a bug because syslog is not an async-signal-safe
function, but maybe we should support this usage scenario as a
quality-of-implementation issue.

Originally reported here in bug 13699 comment 5.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]