From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-fbdev@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.39-rc2, framebuffer] use after free oops
Date: Wed, 20 Apr 2011 10:56:31 +0100 [thread overview]
Message-ID: <20110420105631.70695dfa@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110420080535.3edd11ac@pluto.restena.lu>
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
next prev parent reply other threads:[~2011-04-20 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 11:10 Daniel J Blueman
2011-04-20 5:50 ` Daniel J Blueman
2011-04-20 6:05 ` Bruno Prémont
2011-04-20 9:56 ` Alan Cox [this message]
2011-05-06 2:38 ` Daniel J Blueman
2011-05-07 15:24 ` Anca Emanuel
2011-05-08 11:25 ` Daniel J Blueman
[not found] ` <BANLkTikpswH4cyCVx7h74ttcivdnXZQrUg@mail.gmail.com>
[not found] ` <20110510105001.401d0f66@lxorguk.ukuu.org.uk>
[not found] ` <BANLkTikVSGUs=S3=1nR9gwr4iuAsWM9FuQ@mail.gmail.com>
[not found] ` <BANLkTim49ZU06Upg77-hOzc60tGEYO80wg@mail.gmail.com>
[not found] ` <4DCA8717.5050808@canonical.com>
[not found] ` <20110511140213.73fe6d49@lxorguk.ukuu.org.uk>
[not found] ` <BANLkTinDYcB6xSmPeRtPQcKERxxZaGk=4Q@mail.gmail.com>
2011-05-11 17:04 ` Anca Emanuel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110420105631.70695dfa@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bonbons@linux-vserver.org \
--cc=daniel.blueman@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®