From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rpurdie@rpsys.net, linux-kernel@vger.kernel.org
Subject: Re: backlight: catch invalid input
Date: Sat, 22 Nov 2008 11:37:17 +0100 [thread overview]
Message-ID: <20081122103717.GA8136@elf.ucw.cz> (raw)
In-Reply-To: <20081121155421.152cc555.akpm@linux-foundation.org>
On Fri 2008-11-21 15:54:21, Andrew Morton wrote:
> On Fri, 21 Nov 2008 12:14:14 +0100
> Pavel Machek <pavel@suse.cz> wrote:
>
> >
> > Currently, echo > brightness turns brightness to zero due to
> > insufficient checking. Add a test to catch that.
> >
>
> OK. And what happens if you do
>
> echo wibble > brightness
>
> ?
That's okay, that is catched by tests already existing in there. size
is the size we decoded, count is how many bytes user wrote. If (size
!= count), we return failure.
But there's an exception for whitespace, and missing check for nothing
at all being written.
> > diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
> > index fab0bc8..5c2e23d 100644
> > --- a/drivers/video/backlight/backlight.c
> > +++ b/drivers/video/backlight/backlight.c
> > @@ -86,6 +86,8 @@ static ssize_t backlight_store_power(str
> > int power = simple_strtoul(buf, &endp, 0);
> > size_t size = endp - buf;
> >
> > + if (!size)
> > + return -EINVAL;
> > if (*endp && isspace(*endp))
> > size++;
> > if (size != count)
>
> A better fix would be to use strict_strtoul() and check its return
> value.
Aha, here's the hint :-). Ok, will do.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-11-22 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 11:14 backlight: catch invalid input Pavel Machek
2008-11-21 23:54 ` Andrew Morton
2008-11-22 10:37 ` Pavel Machek [this message]
2008-11-22 20:31 ` Pavel Machek
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=20081122103717.GA8136@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.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 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.