All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Luis Henriques" <luis.henriques@canonical.com>,
	"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	"James Henstridge" <james.henstridge@canonical.com>,
	"Fabien André" <fabien.andre@gmail.com>
Subject: Re: [appleir] BUG: unable to handle kernel NULL pointer dereference
Date: Wed, 06 Nov 2013 18:13:13 +0100	[thread overview]
Message-ID: <1383757993.2554.0.camel@nuvo> (raw)
In-Reply-To: <alpine.LNX.2.00.1311061635160.835@pobox.suse.cz>

On Wed, 2013-11-06 at 16:38 +0100, Jiri Kosina wrote:
> On Tue, 29 Oct 2013, Luis Henriques wrote:
> 
> > James has reported a NULL pointer dereference[1] on the appleir
> > driver.  From the bug report[2] it looks like it is 100%
> > reproducible using a 3.12-rc6 kernel simply by pressing any button on
> > the IR remote.
> > 
> > >From the stack trace, it looks like input_event is invoked with the
> > input_dev parameter set to NULL, which seems to indicate that
> > appleir_input_configured is never invoked.
> > 
> > Any ideas?
> > 
> > [1] https://launchpadlibrarian.net/154942024/macmini-oops.jpg
> > [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244505
> 
> [ adding some more CCs ]
> 
> Okay, so apparently we didn't register with input, but only hiddev / 
> hidraw.
> 
> appleir 0003:05AC:8240.0005: hiddev0,hidraw4: USB HID v1.11 Device [Apple Computer, Inc. IR Receiver] on usb-0000:00:1d.3-2/input0
> 
> Therefore ->input_configured() callback has never been called, and thus we 
> oops due to appleir->input_dev being NULL when the first raw event is 
> reported.
> 
> Could you please provide report descriptor of the device?
> 
> The driver apparently relies on it being registered with hid-input, but 
> for some reason that doesn't happen.

FWIW, my original patch (and driver) was an input driver, not a hid one.
I'm not sure either how the new driver got tested.



  reply	other threads:[~2013-11-06 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 14:51 [appleir] BUG: unable to handle kernel NULL pointer dereference Luis Henriques
2013-11-06 15:38 ` Jiri Kosina
2013-11-06 17:13   ` Bastien Nocera [this message]
2013-11-07  7:52   ` James Henstridge
2013-11-07 15:49     ` Benjamin Tissoires
2013-11-16  0:21       ` Jiri Kosina
2013-11-19 14:33       ` Jiri Kosina
2013-11-21  3:20         ` James Henstridge
2013-11-21  8:59           ` Jiri Kosina
2013-11-21 10:13             ` Luis Henriques
2013-11-22 12:39               ` Jiri Kosina
2013-11-22 12:52                 ` Luis Henriques

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=1383757993.2554.0.camel@nuvo \
    --to=hadess@hadess.net \
    --cc=benjamin.tissoires@redhat.com \
    --cc=fabien.andre@gmail.com \
    --cc=james.henstridge@canonical.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.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.