Anders Kaseorg, thank you for reporting this and helping make Ubuntu better. 
Hardy Server reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following 
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional 
upstream developers to examine the issue. Please do not test the kernel in the 
mainline kernels archive directory daily folder. Once you've tested the 
upstream kernel, please comment on which kernel version specifically you 
tested. If this bug is fixed in the mainline kernel, please add the following 
tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why 
specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

** Tags added: cherry-pick hardy needs-kernel-logs

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1027517

Title:
  fifo: Do not restart open() if it already found a partner

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This race condition is believed to be responsible for a FTBFS of git
  with dash ≥ 0.5.6 (at least on the PPA builders):

  http://git.kernel.org/linus/05d290d66be6ef77a0b962ebecf01911bd984a78
  fifo: Do not restart open() if it already found a partner
  If a parent and child process open the two ends of a fifo, and the child 
immediately exits, the parent may receive a SIGCHLD before its open() returns.  
In that case, we need to make sure that open() will return successfully after 
the SIGCHLD handler returns, instead of throwing EINTR or being restarted.  
Otherwise, the restarted open() would incorrectly wait for a second partner on 
the other end.

  The patch was merged as v3.5~31, v3.4.6~25, and v3.0.38~17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027517/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to