Messages in this thread | | | Date | Wed, 20 Apr 2011 10:56:31 +0100 | From | Alan Cox <> | Subject | Re: [2.6.39-rc2, framebuffer] use after free oops |
| |
On Wed, 20 Apr 2011 08:05:35 +0200 Bruno Prémont <bonbons@linux-vserver.org> wrote:
> On Wed, 20 Apr 2011 13:50:10 Daniel J Blueman <daniel.blueman@gmail.com> wrote: > > Any ideas on how best to address this issue [0], since it causes > > silent corruption, or at best crashes? > > There is probably no easy short-term fix to this...
The short term fix would be to deliberately leak the buffer. That should go into 2.6.39-rc right now with a comment explaining the situation. Otherwise who knows what corruption may occur to user data if unlucky.
The other 'cheat' might be to tweak the API so the removal API isn't a 'destroy' interface but a 'shut down' and has a matching 'restart' one for when the intelfb unloads at which point vga16fb can carry on with the original fb_info 8)
Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |