From: Jarod Wilson <jarod@redhat.com>
To: Mauro Carvalho Chehab <maurochehab@gmail.com>
Cc: Dan Carpenter <error27@gmail.com>, linux-media@vger.kernel.org
Subject: Re: [PATCH v2] IR/imon: remove dead IMON_KEY_RELEASE_OFFSET
Date: Fri, 7 May 2010 09:13:29 -0400 [thread overview]
Message-ID: <20100507131329.GA24239@redhat.com> (raw)
In-Reply-To: <4BE3FEE0.4000502@gmail.com>
On Fri, May 07, 2010 at 08:52:00AM -0300, Mauro Carvalho Chehab wrote:
> Jarod Wilson wrote:
> > On Tue, May 04, 2010 at 06:06:41PM +0200, Dan Carpenter wrote:
> >> On Tue, May 04, 2010 at 10:03:18AM -0400, Jarod Wilson wrote:
> >>> @@ -1205,7 +1204,7 @@ static u32 imon_panel_key_lookup(u64 hw_code)
> >>> if (imon_panel_key_table[i].hw_code == (code | 0xffee))
> >>> break;
> >>>
> >>> - keycode = imon_panel_key_table[i % IMON_KEY_RELEASE_OFFSET].keycode;
> >>> + keycode = imon_panel_key_table[i].keycode;
> >>>
> >>> return keycode;
> >>> }
> >> There is still potentially a problem here because if we don't hit the
> >> break statement, then we're one past the end of the array.
> >
> > D'oh. Okay, here's v2, should fix that buglet too.
> >
> > This hack was used when the imon driver was using internal key lookup
> > routines, but became dead weight when the driver was converted to use
> > ir-core's key lookup routines. These bits simply didn't get removed,
> > drop 'em now.
> >
> > Pointed out by Dan Carpenter.
> >
> > v2: fix possible attempt to access beyond end of key table array,
> > also pointed out by Dan.
>
> -ENOSOB
>
> Please, add your SOB here ;)
D'oh.
Signed-off-by: Jarod Wilson <jarod@redhat.com>
> > ---
> > drivers/media/IR/imon.c | 12 ++++++------
> > 1 files changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/media/IR/imon.c b/drivers/media/IR/imon.c
> > index 27743eb..efe219a 100644
> > --- a/drivers/media/IR/imon.c
> > +++ b/drivers/media/IR/imon.c
> > @@ -55,7 +55,6 @@
> > #define BIT_DURATION 250 /* each bit received is 250us */
> >
> > #define IMON_CLOCK_ENABLE_PACKETS 2
> > -#define IMON_KEY_RELEASE_OFFSET 1000
> >
> > /*** P R O T O T Y P E S ***/
> >
> > @@ -1199,13 +1198,14 @@ static u32 imon_panel_key_lookup(u64 hw_code)
> > {
> > int i;
> > u64 code = be64_to_cpu(hw_code);
> > - u32 keycode;
> > + u32 keycode = KEY_RESERVED;
> >
> > - for (i = 0; i < ARRAY_SIZE(imon_panel_key_table); i++)
> > - if (imon_panel_key_table[i].hw_code == (code | 0xffee))
> > + for (i = 0; i < ARRAY_SIZE(imon_panel_key_table); i++) {
> > + if (imon_panel_key_table[i].hw_code == (code | 0xffee)) {
> > + keycode = imon_panel_key_table[i].keycode;
> > break;
> > -
> > - keycode = imon_panel_key_table[i % IMON_KEY_RELEASE_OFFSET].keycode;
> > + }
> > + }
> >
> > return keycode;
> > }
> >
>
>
> --
>
> Cheers,
> Mauro
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2010-05-07 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 12:20 [-next] [bug report] media/IR/imon: array overflow Dan Carpenter
2010-05-04 14:03 ` [PATCH] IR/imon: remove dead IMON_KEY_RELEASE_OFFSET Jarod Wilson
2010-05-04 16:06 ` Dan Carpenter
2010-05-04 19:17 ` [PATCH v2] " Jarod Wilson
2010-05-07 11:52 ` Mauro Carvalho Chehab
2010-05-07 13:13 ` Jarod Wilson [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=20100507131329.GA24239@redhat.com \
--to=jarod@redhat.com \
--cc=error27@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=maurochehab@gmail.com \
/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).