dragonboard: history daemon dereferences a rogue pointer
Bug #1625805 reported by
kevin gunn
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
history-service (Ubuntu) |
Fix Committed
|
Undecided
|
Gustavo Pichorim Boiko | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Paolo Pisati |
Bug Description
we are running the unity8 session snap on amd64 without any problems.
to setup and reproduce the problem follow the "on Dragonboard" section of
https:/
You can also find the panic signature at line 3276 of the attached syslog.
Related branches
lp://staging/~renatofilho/history-service/snap-path
- Gustavo Pichorim Boiko (community): Approve
- system-apps-ci-bot: Needs Fixing (continuous-integration)
-
Diff: 66 lines (+48/-1)2 files modifieddaemon/pluginmanager.cpp (+1/-1)
snapcraft.yaml (+47/-0)
Changed in linux (Ubuntu): | |
assignee: | nobody → Paolo Pisati (p-pisati) |
summary: |
- arm64 kernel panic for l2 mmu with unity8 session snap + arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well) |
Changed in linux (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
importance: | Undecided → High |
importance: | High → Critical |
milestone: | none → p1 |
Changed in history-service (Ubuntu): | |
assignee: | nobody → Gustavo Pichorim Boiko (boiko) |
Changed in canonical-devices-system-image: | |
importance: | Critical → High |
Changed in history-service (Ubuntu): | |
status: | New → Fix Committed |
no longer affects: | unity8 (Ubuntu) |
no longer affects: | snappy |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Won't Fix |
status: | Won't Fix → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
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 1625805
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.