← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1573117] Re: stress-ng: clone system calls randomly fail with -EINVAL on aarch64

 

SRU: package: https://launchpad.net/~colin-king/+archive/ubuntu/stress-
ng-xenial-sru/+packages

Debdiff: https://launchpadlibrarian.net/255152031/stress-
ng_0.05.23-1_0.05.23-1ubuntu1.diff.gz


** Description changed:

+ [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.

** Also affects: stress-ng (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: stress-ng (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: stress-ng (Ubuntu Xenial)
     Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng (Ubuntu Xenial)
       Status: New => In Progress

-- 
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:
  In Progress

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