← Back to team overview

kernel-packages team mailing list archive

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

 

This bug was fixed in the package linux - 4.0.0-4.6

---------------
linux (4.0.0-4.6) wily; urgency=low

  [ Andy Whitcroft ]

  * Release Tracking Bug
    - LP: #1470233
  * rebase to mainline v4.0.7

  [ Jay Vosburgh ]

  * SAUCE: fan: Proof of concept implementation (v2)
    - LP: #1439706
  * SAUCE: fan: tunnel multiple mapping mode (v3)
    - LP: #1470091

  [ Upstream Kernel Changes ]

  * rebase to v4.0.7
    - LP: #1427680
    - LP: #1462614

 -- Andy Whitcroft <apw@xxxxxxxxxxxxx>  Tue, 30 Jun 2015 16:55:32 +0100

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1418140

Title:
  CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64
  otherwise arm64 cannot run armhf binaries

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  Attempting to run 32bit binaries on arm64 triggers applications to be
  Killed, as the CONFIG_DEFAULT_MMAP_MIN_ADDR used on armhf is not valid
  on arm64.  While this can be overriden via sysctl, the default should
  be sane.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418140/+subscriptions


References