linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Jurij Smakov <jurij@wooyd.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Fw: [Bugme-new] [Bug 7189] New: Inconsistent /proc/fb behavior
Date: Wed, 27 Sep 2006 09:17:05 +0200	[thread overview]
Message-ID: <20060927071705.GA12021@1wt.eu> (raw)
In-Reply-To: <20060927073930.GA23901@droopy.oc.cox.net>

On Wed, Sep 27, 2006 at 12:39:30AM -0700, Jurij Smakov wrote:
> On Tue, Sep 26, 2006 at 01:58:09PM -0700, Andrew Morton wrote:
> > On Sun, 24 Sep 2006 12:31:30 +0200 (CEST)
> > Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> [...]
> > > [PATCH] Correct buffer size limit in fbmem_read_proc()
> > > 
> > > Signed-Off-By: Geert Uytterhoeven <geert@linux-m68k.org>
> > > 
> > > --- linux-2.6.18/drivers/video/fbmem.c.orig	2006-09-04 11:02:45.000000000 +0200
> > > +++ linux-2.6.18/drivers/video/fbmem.c	2006-09-24 12:17:07.000000000 +0200
> > > @@ -554,7 +554,8 @@ static int fbmem_read_proc(char *buf, ch
> > >  	int clen;
> > >  
> > >  	clen = 0;
> > > -	for (fi = registered_fb; fi < &registered_fb[FB_MAX] && len < 4000; fi++)
> > > +	for (fi = registered_fb; fi < &registered_fb[FB_MAX] && clen < 4000;
> > > +	     fi++)
> > >  		if (*fi)
> > >  			clen += sprintf(buf + clen, "%d %s\n",
> > >  				        (*fi)->node,
> > > 
> > 
> > Thanks.   Do we have confirmation that this patch fixes the bug?
> 
> Sorry for not replying sooner. Today I've built a 2.6.18 kernel with this patch 
> and it did fix the problem. Grepping through /proc/fb now works as expected on my 
> Sparc.

Thanks for the feedback, then I'm queueing it for 2.4.34-pre4 too.

Cheers,
Willy


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      reply	other threads:[~2006-09-27  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23  2:47 Fw: [Bugme-new] [Bug 7189] New: Inconsistent /proc/fb behavior Andrew Morton
2006-09-24 10:31 ` Geert Uytterhoeven
2006-09-26 20:58   ` Andrew Morton
2006-09-27  7:39     ` Jurij Smakov
2006-09-27  7:17       ` Willy Tarreau [this message]

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=20060927071705.GA12021@1wt.eu \
    --to=w@1wt.eu \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=jurij@wooyd.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).