public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: [FIX] Re: 2.5.66 new fbcon oops while loading X
Date: Wed, 26 Mar 2003 11:58:40 +0100	[thread overview]
Message-ID: <20030326105840.GA10201@outpost.ds9a.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0303251722321.3789-100000@phoenix.infradead.org>

On Tue, Mar 25, 2003 at 05:23:07PM +0000, James Simmons wrote:
> > While loading X, I get this oops. The weird thing is that I don't use
> > framebuffer. I compiled with gcc 3.2.2 but the code generated looks weird.
> > Virgin gcc 3.2.2 on a pentium III.
> 
> You don't use framebuffer? Can you send me your config. 

Ok, I've found the bug, it is in fb_open() in drivers/video/fbmem.c, it
needs this addition:

        if(fbidx >= FB_MAX)
                return -ENODEV;

Without it, large minor numbers result in access beyond the end of
registered_fb.

On Debian, ls /dev/fb[67] results in:
crw--w--w-    1 root     tty       29, 192 Nov 30  2000 /dev/fb6
crw--w--w-    1 root     tty       29, 224 Nov 30  2000 /dev/fb7

On Red Hat this is: 
crw-------    1 root     root      29,   7 Apr 11  2002 /dev/fb7
crw-------    1 root     root      29,   8 Apr 11  2002 /dev/fb8

Which explains why many don't see this bug.

Regards,

bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
http://netherlabs.nl                         Consulting

  parent reply	other threads:[~2003-03-26 10:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 12:31 2.5.66 new fbcon oops while loading X / possible gcc bug? bert hubert
2003-03-25 17:23 ` James Simmons
2003-03-25 22:15   ` bert hubert
2003-03-26 10:58   ` bert hubert [this message]
2003-03-26 14:54     ` [FIX] Re: 2.5.66 new fbcon oops while loading X Wichert Akkerman
2003-03-26 20:10       ` James Simmons
2003-03-26 22:42         ` Wichert Akkerman
2003-03-27  0:23           ` James Simmons
2003-03-27  9:56             ` Wichert Akkerman
2003-03-26 20:05     ` James Simmons
2003-03-27  9:11       ` [Linux-fbdev-devel] " Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2003-03-27 10:49 Petr Vandrovec
     [not found] ` <BKEGKPICNAKILKJKMHCAIEFBCGAA.Riley@Williams.Name>
2003-04-12  9:39   ` Wichert Akkerman

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=20030326105840.GA10201@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=jsimmons@infradead.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