From: "Henrik Rydberg" <rydberg@bitmath.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org, Daniel Kurtz <djkurtz@chromium.org>,
Benjamin Tissoires <benjamin.tissoires@enac.fr>,
Ping Cheng <pingc@wacom.com>
Subject: Re: linux-next: Tree for Sept 12 (kernel-panic after pressing any key at X login)
Date: Thu, 13 Sep 2012 09:04:10 +0200 [thread overview]
Message-ID: <20120913070410.GA309@polaris.bitmath.org> (raw)
In-Reply-To: <20120913064909.GF17105@core.coreip.homeip.net>
> > >> > this weeks linux-next seems to bring new and new issues, yay :-)!
> > >> >
> > >> > I have taken a photo, but can't say what can have caused.
> > >> > The issue is reproducible...
> > >> > Immediately, after pressing any key (when X-display-manager (lightdm)
> > >> > and X-greeter are up) my machine panics and is no more usable (cold
> > >> > rough brutal killer restart).
> > >> > Note: Using upstart or systemd does not matter.
> > >> >
> > >> > Any pointer to an area where to dig into or any feedback in general is welcome!
> > >> >
> > >> > Kind Regards,
> > >> > - Sedat -
> >
> > Hey, cool. Thanks for the pointer in the source-code and the call-trace!
> > I had reverted [1], but anyway input folks should look at this.
> >
> > Kind Regards,
> > - Sedat -
> >
> > [1] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=b276fc1e875a51e4a9dc3322ed008bf4ae481baf
>
> Henrik,
>
> It looks like your changes are causing the panic.
Indeed, I have pushed the fix below to next already. Thanks for Sedat,
and sorry for not catching this earlier. :-(
Henrik
--
>From ccc6557bfd02efdca4d9dfda6cfdfe5a08d0193b Mon Sep 17 00:00:00 2001
From: Henrik Rydberg <rydberg@euromail.se>
Date: Thu, 13 Sep 2012 08:59:40 +0200
Subject: [PATCH] Input: Fix oops caused by missing null test
Found in linux-next on September 12, thanks Sedat.
Reported-by: Sedat Dilek <sedat.dilek@gmail.com>
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
---
drivers/input/input.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/input.c b/drivers/input/input.c
index 5b66b2f..2dff71b 100644
--- a/drivers/input/input.c
+++ b/drivers/input/input.c
@@ -114,7 +114,7 @@ static unsigned int input_to_handler(struct input_handle *handle,
if (handler->events)
handler->events(handle, vals, count);
- else
+ else if (handler->event)
for (v = vals; v != end; v++)
handler->event(handle, v->type, v->code, v->value);
--
1.7.12
next prev parent reply other threads:[~2012-09-13 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUVEQNPGL7_BbLA-urgP6rFvdOh0SUtYESUv6ZJc+w78Nw@mail.gmail.com>
2012-09-13 5:29 ` linux-next: Tree for Sept 12 (kernel-panic after pressing any key at X login) Sedat Dilek
2012-09-13 6:04 ` Minchan Kim
2012-09-13 6:36 ` Sedat Dilek
2012-09-13 6:49 ` Dmitry Torokhov
2012-09-13 7:04 ` Henrik Rydberg [this message]
2012-09-13 8:18 ` Sedat Dilek
2012-09-13 9:05 ` Sedat Dilek
2012-09-13 12:24 ` Stephen Rothwell
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=20120913070410.GA309@polaris.bitmath.org \
--to=rydberg@bitmath.se \
--cc=benjamin.tissoires@enac.fr \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=pingc@wacom.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).