| 2016-06-07 22:12:32 |
dann frazier |
bug |
|
|
added bug |
| 2016-06-07 22:12:39 |
dann frazier |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-06-07 22:12:39 |
dann frazier |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2016-06-07 22:12:46 |
dann frazier |
linux (Ubuntu Xenial): status |
New |
Incomplete |
|
| 2016-06-07 22:12:49 |
dann frazier |
linux (Ubuntu Xenial): status |
Incomplete |
In Progress |
|
| 2016-06-07 22:12:53 |
dann frazier |
linux (Ubuntu): status |
In Progress |
Confirmed |
|
| 2016-06-07 22:12:56 |
dann frazier |
linux (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-06-07 22:12:58 |
dann frazier |
linux (Ubuntu Xenial): assignee |
|
dann frazier (dannf) |
|
| 2016-06-09 21:07:43 |
dann frazier |
linux (Ubuntu Xenial): status |
In Progress |
Won't Fix |
|
| 2016-06-09 21:07:55 |
dann frazier |
description |
[Impact]
The arm-smmu driver doesn't allow 2 different devices (SMMU 0/1) to share a namespace. So if 2 devices are connected to same SMMU, it may lead to memory corruption.
[Test Case]
[Regression Risk] |
The arm-smmu driver doesn't allow 2 different devices (SMMU 0/1) to share a namespace. So if 2 devices are connected to same SMMU, it may lead to memory corruption. |
|
| 2018-03-12 21:30:12 |
dann frazier |
linux (Ubuntu): status |
Confirmed |
Fix Released |
|
