group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1573117@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package stress-ng - 0.05.23-1ubuntu2

---------------
stress-ng (0.05.23-1ubuntu2) xenial; urgency=medium

  * Fix alignment mask to ensure stacks are 16 byte aligned (LP: #1573117)
    - incorrect mask used in previous fix, now using correct mask

stress-ng (0.05.23-1ubuntu1) xenial; urgency=medium

  * Ensure all clone() calls are 16 byte aligned for aarch64 (LP: #1573117)
  * stress-mmap: handle SIGBUS signals (LP: #1569468)

 -- Colin King <colin.king@xxxxxxxxxxxxx>  Tue, 26 Apr 2016 12:16:47
+0100

** Changed in: stress-ng (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1573117

Title:
  stress-ng: clone system calls randomly fail with -EINVAL on aarch64

Status in stress-ng package in Ubuntu:
  Fix Committed
Status in stress-ng source package in Xenial:
  Fix Released

Bug description:
  [SRU] Xenial

  Getting -EINVAL on stressors that call clone() on aarch64. Turns out
  that the clone() thread's stack has to be 16 byte aligned.

  [REPODUCER + FIX]
  For example, run:

  stress-ng --vm-rw 1 -v

  Without the fix, this can randomly exit with -EINVAL when the stack
  being passed to the clone() system call is not aligned on a 16 byte
  boundary.

  With the fix, the clone() system call works fine and the stressor will
  run.

  [REGRESSION POTENIAL]
  Minimal. I have exhaustively tested this on multiple platforms/architectures and the fix ensures that the stack is aligned correctly.  stress-ng is a leaf project in universe and this fix only touches 3 of the stress-ng stressors that use the clone() system call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1573117/+subscriptions