stress-ng: aio stressor may get a pending SIGUSR1 before it exits, so don't cancel the handler

[Colin Ian King]

A loaded system may trigger a SIGUSR1 pending aio signal after we've cancelled the handler and before the stress process exits which is not useful. Just don't cancel the handler.

[Colin Ian King (colin-king)]

Fix committed, commit http://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=8ea33dfc75e24d0b360662e627bce5d1202cba47

[Launchpad Janitor (janitor)]

This bug was fixed in the package stress-ng - 0.05.17-1

---------------
stress-ng (0.05.17-1) unstable; urgency=medium

  * Makefile: bump version
  * stress-aio: don't cancel the signal handler before exiting (LP: #1547108)
  * stress-lockf: don't return failure if we get a timeout (LP: #154107)
  * stress-aio: don't return failure if we get a timeout (LP: #1547090)
  * Check for ENOMEM ENOSPC errors during init (LP: #1547062)
  * make stress_temp_dir_mk and stress_temp_dir_rm return -errno on failure
  * stress-dentry: fix file striding on clean-up (LP: #1547004)
  * Add stress_get_prime64 to stress-ng header
  * Add stress_get_prime64 to find a prime for filename striding
  * typedef possibly missing __kernel_long_t and __kernel_ulong_t
  * Add <linux/posix_types.h> for linux builds
  * stress-aio-linux: fix clang scan-build warning
  * Makefile: only do build time config detection when building target

 -- Colin King <email address hidden> Thu, 18 Feb 2016 17:52:11 +0000