[Bugme-new] [Bug 6766] New: read(0, ..) after fork() can cause the system to hang

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=6766

           Summary: read(0,..) after fork() can cause the system to hang
    Kernel Version: 2.6.17
            Status: NEW
          Severity: normal
             Owner: io_other at kernel-bugs.osdl.org
         Submitter: irush at cs.huji.ac.il


Most recent kernel where this bug did not occur: 2.6.14
Distribution: debian testing (vanilla kernel)
Hardware Environment: N/A
Software Environment:
Problem Description:
After forking, if the child process calls read(0,...), and then the parent
exits, the child might not respond to KILL signal and stay opened consuming more
and more resourses, eventually freezing the system which forces a reboot.

This happens in about 1 out of 7 runs (in average).
Tested on several hardwares.

Steps to reproduce:
Attached c code.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.