Comment 6 for bug 737676

Confirmed to be fixed using QRT r1242 for testing...

Before (2.6.35-28.50-generic): sudo ./test-kernel-security.py -v
...
ptrace of child works from parent threads (LP: #737676) ... FAIL
…
======================================================================
FAIL: ptrace of child works from parent threads (LP: #737676)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1049, in test_093_ptrace_restriction_parent_via_thread
    self.assertShellExitEquals(expected, ['sudo','-u',os.environ['SUDO_USER'],'./thread-prctl','0','0'])
  File "/home/kees/qa-regression-testing/scripts/testlib.py", line 839, in assertShellExitEquals
    self.assertEquals(expected, rc, msg + result + report)
AssertionError: Got exit code 2, expected 0
Command: 'sudo', '-u', 'kees', './thread-prctl', '0', '0'
Output:
will fork tracee from tracer
will issue ptrace from tracer thread
master is 11021
master waiting for tracer to finish
tracer is 11022
tracer 11022 waiting
forking tracee from tracer
tracee 11024 reading tracer pid
tracee 11024 started (expecting 11022 as tracer)
tracee triggering tracer
tracer to PTRACE_ATTACH my tracee 11024
tracer ptrace attach has failed: Operation not permitted
master waiting for tracee to finish
master saw rc 2 from tracer
tracee waiting for master
tracee finished (stop)

----------------------------------------------------------------------
Ran 48 tests in 27.344s

FAILED (failures=1)

After (2.6.35-29.51-generic): $ sudo ./test-kernel-security.py -v
...
ptrace of child works from parent threads (LP: #737676) ... ok
...