Activity log for bug #1591804

Date Who What changed Old value New value Message
2016-06-13 02:09:20 XiongZhang bug added bug
2016-09-22 00:06:45 Leann Ogasawara information type Proprietary Public
2016-09-22 00:06:53 Leann Ogasawara bug task added linux (Ubuntu)
2016-09-22 00:07:07 Leann Ogasawara linux (Ubuntu): status New Fix Released
2016-09-22 00:07:15 Leann Ogasawara intel: status New Fix Released
2016-09-22 00:24:05 XiongZhang description Memory Protection Keys for Userspace (PKU aka PKEYs) is a Skylake-SP server feature that provides a mechanism for enforcing page-based protections, but without requiring modification of the page tables when an application changes protection domains. It works by dedicating 4 previously ignored bits in each page table entry to a "protection key", giving 16 possible keys. There is also a new user-accessible register (PKRU) with two separate bits (Access Disable and Write Disable) for each key.Being a CPU register, PKRU is inherently thread-local,potentially giving each thread a different set of protectionsfrom every other thread. There are two new instructions (RDPKRU/WRPKRU) for reading and writing to the new register. The feature is only available in 64-bit mode, even though there is theoretically space in the PAE PTEs. These permissions are enforced on data access only and have no effect on instruction fetches. HW: Purley Upstream status: v4.6 kernel implement basic and execute-only support v4.8 kernel will have new interface Memory Protection Keys for Userspace (PKU aka PKEYs) is a Skylake-SP server feature that provides a mechanism for enforcing page-based protections, but without requiring modification of the page tables when an application changes protection domains. It works by dedicating 4 previously ignored bits in each page table entry to a "protection key", giving 16 possible keys. There is also a new user-accessible register (PKRU) with two separate bits (Access Disable and Write Disable) for each key.Being a CPU register, PKRU is inherently thread-local,potentially giving each thread a different set of protectionsfrom every other thread. There are two new instructions (RDPKRU/WRPKRU) for reading and writing to the new register. The feature is only available in 64-bit mode, even though there is theoretically space in the PAE PTEs. These permissions are enforced on data access only and have no effect on instruction fetches. HW: Purley Upstream status: v4.6 kernel implement basic and execute-only support v4.9 kernel will have new interface
2016-09-22 00:24:09 XiongZhang linux (Ubuntu): status Fix Released New
2016-09-22 00:24:12 XiongZhang intel: status Fix Released New
2016-09-22 00:30:11 Brad Figg linux (Ubuntu): status New Incomplete
2016-10-19 14:46:18 Tim Gardner linux (Ubuntu): status Incomplete In Progress
2016-10-19 14:46:18 Tim Gardner linux (Ubuntu): assignee Tim Gardner (timg-tpi)
2016-10-19 14:46:31 Tim Gardner nominated for series Ubuntu Zesty
2016-10-19 14:46:31 Tim Gardner bug task added linux (Ubuntu Zesty)
2016-10-19 14:46:31 Tim Gardner nominated for series Ubuntu Yakkety
2016-10-19 14:46:31 Tim Gardner bug task added linux (Ubuntu Yakkety)
2016-10-19 14:46:39 Tim Gardner linux (Ubuntu Zesty): status In Progress Fix Released
2016-10-19 14:46:48 Tim Gardner linux (Ubuntu Yakkety): status New In Progress
2016-10-19 14:46:48 Tim Gardner linux (Ubuntu Yakkety): assignee Tim Gardner (timg-tpi)
2016-11-03 21:50:10 Tim Gardner linux (Ubuntu Yakkety): status In Progress Fix Committed
2016-11-16 10:07:51 Luis Henriques tags verification-needed-yakkety
2016-11-30 02:05:55 Launchpad Janitor linux (Ubuntu Yakkety): status Fix Committed Fix Released
2016-11-30 02:05:55 Launchpad Janitor cve linked 2016-7425
2017-03-30 12:31:37 Leann Ogasawara intel: status New Fix Released