From: Dan Carpenter <dan.carpenter@oracle.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] mtd/docg3: off by one in doc_register_sysfs()
Date: Sat, 24 Oct 2015 17:49:12 +0000 [thread overview]
Message-ID: <20151024174912.GD7289@mwanda> (raw)
In-Reply-To: <87twpgwahr.fsf@belgarion.home>
On Sat, Oct 24, 2015 at 11:49:27AM +0200, Robert Jarzmik wrote:
> Dan Carpenter <dan.carpenter@oracle.com> writes:
>
> > Smatch found a bug in the error handling:
> >
> > drivers/mtd/devices/docg3.c:1634 doc_register_sysfs()
> > error: buffer overflow 'doc_sys_attrs' 4 <= 4
> >
> > The problem is that if the very last device_create_file() fails, then we
> > are beyond the end of the array. Actually, any time i = 3 then there
> > is a problem. We can fix this an simplify the code at the same time by
> > moving the !ret conditions out of the for loops and using a goto
> > instead.
>
> Hi Dan,
>
> I must admit I don't see the issue here :
> - if the last device_create_file() fail, we have :
> - i = 3, ret = -Exxx
> - doc_sys_attrs[floor][0] is populated
> - doc_sys_attrs[floor][1] is populated
> - doc_sys_attrs[floor][2] is populated
> - doc_sys_attrs[floor][3] is probably NULL
We increment "i" to 4.
We increment "floor" here before the next loop exits.
> - next for loop exits
>
> The while loop takes over :
> - first iteration :
> - --i => i = 2
Actually --i is 3 and "floor" is out of bounds.
> device_remove_file(dev, &doc_sys_attrs[floor][2]);
> - then the remaining attributes
>
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] mtd/docg3: off by one in doc_register_sysfs()
Date: Sat, 24 Oct 2015 20:49:12 +0300 [thread overview]
Message-ID: <20151024174912.GD7289@mwanda> (raw)
In-Reply-To: <87twpgwahr.fsf@belgarion.home>
On Sat, Oct 24, 2015 at 11:49:27AM +0200, Robert Jarzmik wrote:
> Dan Carpenter <dan.carpenter@oracle.com> writes:
>
> > Smatch found a bug in the error handling:
> >
> > drivers/mtd/devices/docg3.c:1634 doc_register_sysfs()
> > error: buffer overflow 'doc_sys_attrs' 4 <= 4
> >
> > The problem is that if the very last device_create_file() fails, then we
> > are beyond the end of the array. Actually, any time i == 3 then there
> > is a problem. We can fix this an simplify the code at the same time by
> > moving the !ret conditions out of the for loops and using a goto
> > instead.
>
> Hi Dan,
>
> I must admit I don't see the issue here :
> - if the last device_create_file() fail, we have :
> - i = 3, ret = -Exxx
> - doc_sys_attrs[floor][0] is populated
> - doc_sys_attrs[floor][1] is populated
> - doc_sys_attrs[floor][2] is populated
> - doc_sys_attrs[floor][3] is probably NULL
We increment "i" to 4.
We increment "floor" here before the next loop exits.
> - next for loop exits
>
> The while loop takes over :
> - first iteration :
> - --i => i = 2
Actually --i is 3 and "floor" is out of bounds.
> device_remove_file(dev, &doc_sys_attrs[floor][2]);
> - then the remaining attributes
>
regards,
dan carpenter
next prev parent reply other threads:[~2015-10-24 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 10:20 [patch] mtd/docg3: off by one in doc_register_sysfs() Dan Carpenter
2015-10-19 10:20 ` Dan Carpenter
2015-10-24 9:49 ` Robert Jarzmik
2015-10-24 9:49 ` Robert Jarzmik
2015-10-24 17:49 ` Dan Carpenter [this message]
2015-10-24 17:49 ` Dan Carpenter
2015-10-25 7:54 ` Robert Jarzmik
2015-10-25 7:54 ` Robert Jarzmik
2015-10-26 18:45 ` Brian Norris
2015-10-26 18:45 ` Brian Norris
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=20151024174912.GD7289@mwanda \
--to=dan.carpenter@oracle.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.