All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ping Cheng <pinglinux@gmail.com>
Cc: Chris J Arges <christopherarges@gmail.com>,
	linux-input <linux-input@vger.kernel.org>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	Ping Cheng <pingc@wacom.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Input: wacom_w8001 - Ignore bogus idx values in interrupt
Date: Mon, 23 May 2016 09:52:26 -0700	[thread overview]
Message-ID: <20160523165226.GC20465@dtor-ws> (raw)
In-Reply-To: <CAF8JNhLzEKmQ-D-o6TYkerJ+=PfLYdHKpB40yU3ohP=sp00ozQ@mail.gmail.com>

On Sun, May 22, 2016 at 10:21:45PM -0700, Ping Cheng wrote:
> Hi Chris,
> 
> On Sun, May 22, 2016 at 6:42 PM, Chris J Arges
> <christopherarges@gmail.com> wrote:
> > I've noticed crashes when using my x60t using a coreboot bios. When using
> > the pen I can produce a crash simply by tapping a few times. This
> > generates an event which has an idx of 0xc. This in turn crashes the
> > machine because the array access is greater than W8001_MAX_LENGTH. This
> > patch checks for bogus values and filters them in order to prevent crashes.
> 
> Thank you for submitting a patch in addition to reporting the issue.
> 
> > Signed-off-by: Chris J Arges <christopherarges@gmail.com>
> > ---
> >  drivers/input/touchscreen/wacom_w8001.c | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> >
> > diff --git a/drivers/input/touchscreen/wacom_w8001.c b/drivers/input/touchscreen/wacom_w8001.c
> > index bab3c6a..c858200 100644
> > --- a/drivers/input/touchscreen/wacom_w8001.c
> > +++ b/drivers/input/touchscreen/wacom_w8001.c
> > @@ -283,6 +283,15 @@ static irqreturn_t w8001_interrupt(struct serio *serio,
> >         unsigned char tmp;
> >
> >         w8001->data[w8001->idx] = data;
> > +
> > +       /* ignore bogus idx values */
> > +       if (w8001->idx >= W8001_MAX_LENGTH) {
> > +               pr_info("w8001: ignored interrupt: data 0x%02x idx %d\n", data,
> > +                       w8001->idx);
> > +               w8001->idx = 0;
> > +               return IRQ_HANDLED;
> > +       }
> > +
> 
> I don't have an x60t system to test with. I wonder if your system
> supports two finger touch or not. We at least have a bug in the code
> since W8001_MAX_LENGTH should be 13 instead of 11. How come no one had
> encountered that issue before?
> 
> I'm going to email a patch to the list. Please test it and let us know
> your result. Maybe we still need your patch if your device doesn't
> support two finger touch or the idx=0xc can't be fixed by
> W8001_MAX_LENGTH=13.

Just so we are clear this version of the patch is buggy as we check the
index only after [potentially] writing past the array bounds of
w8001->data[].

Thanks.

-- 
Dmitry

  reply	other threads:[~2016-05-23 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  1:42 [PATCH] Input: wacom_w8001 - Ignore bogus idx values in interrupt Chris J Arges
2016-05-23  5:21 ` Ping Cheng
2016-05-23 16:52   ` Dmitry Torokhov [this message]
2016-05-23 18:00     ` Ping Cheng

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=20160523165226.GC20465@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=benjamin.tissoires@gmail.com \
    --cc=christopherarges@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=pingc@wacom.com \
    --cc=pinglinux@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 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.