From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Samuel.CUELLA@supinfo.com, adaplas@gmail.com,
linux-kernel@vger.kernel.org, trivial@kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 2.6.28 ] i810: kernel crash fix when struct fb_var_screeninfo is supplied
Date: Wed, 4 Mar 2009 15:17:07 -0800 [thread overview]
Message-ID: <20090304151707.804b5e84.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0903042353350.4971@jikos.suse.cz>
On Wed, 4 Mar 2009 23:54:49 +0100 (CET)
Jiri Kosina <jkosina@suse.cz> wrote:
> On Wed, 4 Mar 2009, Andrew Morton wrote:
>
> > > This is not appropriate for trivial tree. CCing akpm and lkml.
> > I don't have a copy of the original patch.
>
> This is what I got from Samuel (and rejected it for trivial tree, not
> being trivial enough :) )
>
ok, thanks.
> --- linux-2.6.28/drivers/video/i810/i810_main.c.orig 2009-02-26 15:23:03.000000000 +0100
> +++ linux-2.6.28/drivers/video/i810/i810_main.c 2009-02-26 14:50:06.000000000 +0100
> @@ -993,6 +993,8 @@ static int i810_check_params(struct fb_v
> struct i810fb_par *par = info->par;
> int line_length, vidmem, mode_valid = 0, retval = 0;
> u32 vyres = var->yres_virtual, vxres = var->xres_virtual;
> + u32 yres = info->var.yres;
> +
> /*
> * Memory limit
> */
So we have a file-wide static called `yres' - seems a bit dangerous.
Rather than defining a local which shadows the global, it would be
clearer to do it in this equivalent way, yes?
--- a/drivers/video/i810/i810_main.c~i810-fix-kernel-crash-fix-when-struct-fb_var_screeninfo-is-supplied
+++ a/drivers/video/i810/i810_main.c
@@ -993,6 +993,7 @@ static int i810_check_params(struct fb_v
struct i810fb_par *par = info->par;
int line_length, vidmem, mode_valid = 0, retval = 0;
u32 vyres = var->yres_virtual, vxres = var->xres_virtual;
+
/*
* Memory limit
*/
@@ -1002,12 +1003,12 @@ static int i810_check_params(struct fb_v
if (vidmem > par->fb.size) {
vyres = par->fb.size/line_length;
if (vyres < var->yres) {
- vyres = yres;
+ vyres = info->var.yres;
vxres = par->fb.size/vyres;
vxres /= var->bits_per_pixel >> 3;
line_length = get_line_length(par, vxres,
var->bits_per_pixel);
- vidmem = line_length * yres;
+ vidmem = line_length * info->var.yres;
if (vxres < var->xres) {
printk("i810fb: required video memory, "
"%d bytes, for %dx%d-%d (virtual) "
_
This assumes that the original change was actually correct. Should
both sites whcih use the global `yres' have been converted to use
info->var.yres, or just one of them?
next prev parent reply other threads:[~2009-03-04 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02E43B9E8855E74E886358B5184B4CC9104620C0@mail2-aub1fr.esi-supinfo.com>
[not found] ` <alpine.LNX.2.00.0903041108470.4971@jikos.suse.cz>
2009-03-04 22:20 ` [PATCH 2.6.28 ] i810: kernel crash fix when struct fb_var_screeninfo is supplied Andrew Morton
2009-03-04 22:54 ` Jiri Kosina
2009-03-04 23:17 ` Andrew Morton [this message]
2009-03-04 23:45 ` RE : " CUELLA Samuel
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=20090304151707.804b5e84.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Samuel.CUELLA@supinfo.com \
--cc=adaplas@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).