diff options
| author | Dave Airlie <airlied@redhat.com> | 2013-01-24 10:12:41 +0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-02-28 17:38:39 +0400 |
| commit | e0cfce95ff8e4789c35c02e7c1e0e88bc48ce54b (patch) | |
| tree | 80c143b38383c6c08922e46bba20e44c517108f0 /drivers/clk | |
| parent | b175bab7e14904a9fc09128e0f88de89efdf9395 (diff) | |
| download | linux-e0cfce95ff8e4789c35c02e7c1e0e88bc48ce54b.tar.xz | |
fbcon: don't lose the console font across generic->chip driver switch
commit ae1287865f5361fa138d4d3b1b6277908b54eac9 upstream.
If grub2 loads efifb/vesafb, then when systemd starts it can set the console
font on that framebuffer device, however when we then load the native KMS
driver, the first thing it does is tear down the generic framebuffer driver.
The thing is the generic code is doing the right thing, it frees the font
because otherwise it would leak memory. However we can assume that if you
are removing the generic firmware driver (vesa/efi/offb), that a new driver
*should* be loading soon after, so we effectively leak the font.
However the old code left a dangling pointer in vc->vc_font.data and we
can now reuse that dangling pointer to load the font into the new
driver, now that we aren't freeing it.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=892340
Signed-off-by: Dave Airlie <airlied@redhat.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/clk')
0 files changed, 0 insertions, 0 deletions