Please enable kconfig X86_LEGACY_VM86 for i386
Bug #1499089 reported by
Andrew Bird
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Wishlist
|
Tim Gardner | ||
Wily |
Fix Released
|
Wishlist
|
Tim Gardner | ||
Xenial |
Fix Released
|
Wishlist
|
Tim Gardner | ||
Yakkety |
Fix Released
|
Wishlist
|
Tim Gardner |
Bug Description
In order for dosemu to reach maximum performance (a > 10x speedup) please enable kconfig X86_LEGACY_VM86 in the kernel. As of this commit http://
the overzealous kconfig message that seemed to suggest that the vm86() syscall was a security hazard in itself has been revised to reflect reality. Also please note that even if this kconfig option is enabled the runtime default is still off as vm86 is only actually enabled if the sysctl vm.mmap_min_addr is set to 0. That said, allowing vm.mmap_min_addr=0 is a known security risk and enabling the vm86() syscall to operate additionally would add little value to any potential attacker.
Changed in linux (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | Confirmed → Triaged |
tags: |
added: verification-done-wily removed: verification-needed-wily |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | New → In Progress |
Changed in linux (Ubuntu Yakkety): | |
status: | Fix Released → In Progress |
milestone: | none → ubuntu-16.10 |
Changed in linux (Ubuntu Yakkety): | |
milestone: | ubuntu-16.10 → ubuntu-16.05 |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Wishlist |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu Yakkety): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1499089
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.