[Bug 1397250] Re: SIGPIPE not caught in do_atfork_child()

Chris J Arges 1397250 at bugs.launchpad.net
Wed Nov 2 13:19:55 UTC 2016


Hello Marcello, or anyone else affected,

Accepted libnss-ldap into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/libnss-
ldap/264-2.2ubuntu4.14.04.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libnss-ldap (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1397250

Title:
  SIGPIPE not caught in do_atfork_child()

Status in nss_ldap:
  Fix Released
Status in libnss-ldap package in Ubuntu:
  Fix Released
Status in libnss-ldap source package in Trusty:
  Fix Committed
Status in libnss-ldap source package in Xenial:
  Won't Fix
Status in libnss-ldap source package in Yakkety:
  Won't Fix

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nss-ldap/+bug/1397250/+subscriptions



More information about the foundations-bugs mailing list