With previous xenial kernels:

XFAIL: nptl/tst-signal6
XFAIL: nptl/tst-thread-exit-clobber
XFAIL: signal/tst-minsigstksz-1
XFAIL: signal/tst-minsigstksz-2
XFAIL: signal/tst-minsigstksz-3
XFAIL: signal/tst-minsigstksz-3a
XFAIL: signal/tst-minsigstksz-4
XFAIL: support/tst-xsigstack

With the kernel in xenial-proposed:

XPASS: nptl/tst-signal6
XPASS: nptl/tst-thread-exit-clobber
XPASS: signal/tst-minsigstksz-1
XPASS: signal/tst-minsigstksz-2
XPASS: signal/tst-minsigstksz-3
XPASS: signal/tst-minsigstksz-3a
XPASS: signal/tst-minsigstksz-4
XPASS: support/tst-xsigstack

I declare this a resounding success and will adjust the tags

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

** Changed in: linux (Ubuntu)
       Status: Confirmed => Fix Released

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

  arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux package in Debian:
  Fix Released

Bug description:

  The arm64 kernel allows one to run aarch32 processes on an aarch64
  processor, using the standard 32/64-bit syscall compatibility. However
  this compat layer does not correctly validate the arguments of the
  sigaltstack syscall which can result in process failures.

  [Test Case]

  The simple reproducer from https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=904385 triggers a memory allocation error with
  the current Xenial 4.4 kernel.


  Backport the following two upstream commits:
  24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ
  22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in 

  With these two commits, the reproducer no longer fails.

  [Regression Potential]

  Low. the modifications are trivial and the two patches have been in
  upstream for quite a while.

  [Original Description]

  This seems to have been fixed in 4.15 (finally), but is still an issue
  in the 4.4 kernel used on our builders, and possibly others as well
  (needs investigation).

  The original Debian bug report linked has more info, as well as the
  patchset on lkml at https://lkml.org/lkml/2018/7/25/409

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to