[Bug 1397250] [NEW] SIGPIPE not caught in do_atfork_child()

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Jon Grimm (jgrimm):

[Impact]

 * If a process using libnss-ldap calls fork() and SIGPIPE was blocked, 
   the atfork() handler in the child process failed to catch the SIGPIPE 
   as it was supposed to do, that is in the call to  do_close_no_unbind().
   So that, the uncaught SIGPIPE will be eventually delivered when the
   child unblocks signals. This usually make the child process die
   unexpectedly.

 * This is only reproducible when ldap is configured for STARTTLS.

 * Upstream fix has been long integrated.

[Test Case]

 * See https://bugs.launchpad.net/ubuntu/trusty/+source/libnss-
ldap/+bug/1397250/comments/19


[Regression Potential] 

 * Fix has been upstream since 2010, and limited to path of child
   forking, and SIGPIPE is blocked. No consequent bugs or regressions
   in the upstream blamed on this change.  


[Other Info]
 
 * I'm currently limiting my SRU to trusty, as I'm unable to 
   recreate the bug on xenial.  Even so, I have tested the fixed 
   code on xenial to ensure there was no regression with the testcase.

 * Will look at fixing xenial too, IFF someone comes forward able to
   reproduce the bug/validate the fix.

** Affects: nss-ldap
     Importance: Medium
         Status: Fix Released

** Affects: libnss-ldap (Ubuntu)
     Importance: High
     Assignee: Jon Grimm (jgrimm)
         Status: Fix Released

** Affects: libnss-ldap (Ubuntu Trusty)
     Importance: High
     Assignee: Jon Grimm (jgrimm)
         Status: Confirmed

** Affects: libnss-ldap (Ubuntu Xenial)
     Importance: Undecided
         Status: Won't Fix

** Affects: libnss-ldap (Ubuntu Yakkety)
     Importance: Undecided
         Status: Won't Fix


** Tags: atfork fork sigpipe
-- 
SIGPIPE not caught in do_atfork_child()
https://bugs.launchpad.net/bugs/1397250
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.