Fixup vesafb initialization patch which was mistakenly dropped.
Bug #611471 reported by
Brad Figg
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Hardy |
Won't Fix
|
Low
|
Unassigned | ||
Karmic |
Fix Released
|
Low
|
Unassigned | ||
Lucid |
Fix Released
|
Low
|
Unassigned |
Bug Description
SRU Justification
Since dapper we have carried a vesafb modularization patch. This allows
us to make vesafb a module so we can control its insertion. When this
patch was rolled forward somewhere between dapper and hardy part of the
patch was lost. Such that we do not allocate sufficient memory for the
local info structure. This can lead to memory corruption and will lead
to a panic on unload of the module.
Please apply the attached patch to correct this problem.
TEST CASE: TBD
tags: | added: patch |
tags: | added: kj-triage |
Changed in linux (Ubuntu Lucid): | |
importance: | Undecided → Low |
status: | New → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
tags: | added: testcase |
To post a comment you must log in.
Seems to have been uploaded to jaunty-proposed
needs debdiff on bug
needs a test case
needs approval from ubuntu-sru (subscribed)