From: Francisco Jerez <currojerez@riseup.net>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: nouveau@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
Dan Carpenter <error27@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Nouveau] [PATCH] drm/nouveau: fix pramdac_table range checking
Date: Wed, 17 Feb 2010 18:36:06 +0000 [thread overview]
Message-ID: <87vddvyajt.fsf@riseup.net> (raw)
In-Reply-To: <20100215222041.GA2823@joi.lan> (Marcin Slusarz's message of "Mon, 15 Feb 2010 23:20:41 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 2825 bytes --]
Marcin Slusarz <marcin.slusarz@gmail.com> writes:
> On Mon, Feb 15, 2010 at 03:40:56PM +0300, Dan Carpenter wrote:
>> This is the results from:
>> make C=1 CHECK="/path/to/smatch -p=kernel" bzImage modules | tee warns.txt
>> grep -w overflow warns.txt | uniq -f 3 | tee err-list
>>
>> I hacked on the buffer overflow check last weekend and these are the
>> results. It has way more false positives than the other bug lists
>> I've posted, but it's still kinda neat.
>>
>> It works like this:
>>
>> lib/zlib_inflate/inftrees.c
>> 112 for (min = 1; min <= MAXBITS; min++)
>> 113 if (count[min] != 0) break;
>> 114 if (root < min) root = min;
>> smatch thinks "min" can be MAXBITS here.
>>
>> One bad thing is that if you have code like:
>> if (foo == 42)
>> frob();
>> Smatch thinks that "foo" can be 43 after the if statement.
>>
>> The format is:
>> file.c +<line> function(<lines into function>) warning 'array_name' <array size> <= <offset>
>>
>> regards,
>> dan carpenter
>>
>> Previous bug lists:
>> * Putting too much data on the stack
>> http://lkml.indiana.edu/hypermail/linux/kernel/1002.1/01252.html
>>
>> * Assigning negative values to unsigned variables
>> http://lkml.indiana.edu/hypermail/linux/kernel/1001.3/01222.html
>>
>> * Doing dma on the stack
>> http://lkml.indiana.edu/hypermail/linux/kernel/1001.3/01231.html
>>
>> * Dereferencing variables before verifying they are not null
>> http://lkml.indiana.edu/hypermail/linux/kernel/1001.3/01980.html
>>
>> (...)
>> drivers/gpu/drm/nouveau/nouveau_bios.c +770 get_tmds_index_reg(36) error: buffer overflow 'pramdac_table' 4 <= 4
>> (...)
>
> ---
> From: Marcin Slusarz <marcin.slusarz@gmail.com>
> Subject: [PATCH] drm/nouveau: fix pramdac_table range checking
>
> get_tmds_index_reg reads some value from stack when mlv happens
> to be equal to size of pramdac_table array. Fix it.
>
> Reported-by: Dan Carpenter <error27@gmail.com>
> Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
> ---
> drivers/gpu/drm/nouveau/nouveau_bios.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.c b/drivers/gpu/drm/nouveau/nouveau_bios.c
> index 2cd0fad..e7be506 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_bios.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_bios.c
> @@ -762,7 +762,7 @@ static uint32_t get_tmds_index_reg(struct drm_device *dev, uint8_t mlv)
> dacoffset ^= 8;
> return 0x6808b0 + dacoffset;
> } else {
> - if (mlv > ARRAY_SIZE(pramdac_table)) {
> + if (mlv >= ARRAY_SIZE(pramdac_table)) {
> NV_ERROR(dev, "Magic Lookup Value too big (%02X)\n",
> mlv);
> return 0;
Thanks. I've pushed all the three patches.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-02-17 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 12:40 bug list: range checking issues Dan Carpenter
2010-02-15 13:47 ` Alexey Dobriyan
2010-02-15 14:04 ` Dan Carpenter
2010-02-15 22:08 ` Dave Chinner
2010-02-15 22:20 ` [PATCH] drm/nouveau: fix pramdac_table range checking Marcin Slusarz
2010-02-17 18:36 ` Francisco Jerez [this message]
2010-02-15 22:22 ` [PATCH] drm/nouveau: fix nouveau_i2c_find bounds checking Marcin Slusarz
2010-02-16 5:42 ` bug list: range checking issues Dan Carpenter
2010-02-16 10:00 ` Clemens Ladisch
2010-02-16 11:02 ` Jaroslav Kysela
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=87vddvyajt.fsf@riseup.net \
--to=currojerez@riseup.net \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=nouveau@lists.freedesktop.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).