From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
benjamin.tissoires@redhat.com, aduggan@synaptics.com,
jkosina@suse.cz
Subject: Re: NULL pointer dereference in i2c-hid
Date: Thu, 11 Dec 2014 10:58:01 +0200 [thread overview]
Message-ID: <20141211085801.GR1300@lahna.fi.intel.com> (raw)
In-Reply-To: <31518562.V5Oyo0POsI@xps13>
On Wed, Dec 10, 2014 at 06:04:51PM +0100, Gabriele Mazzotta wrote:
> my laptop uses a touchpad that needs hid-rmi along with i2c-hid to work.
> i2c-hid and hid-rmi can be loaded and unloaded independelty from each
> other, however since 34f439e4afcd ("HID: i2c-hid: add runtime PM support")
> if I unload hid-rmi and after it I also unload i2c-hid, I get a NULL
> pointer dereference.
I'll look into this.
I can reproduce this easily with i2c-hid + hid-multitouch following your
directions.
next prev parent reply other threads:[~2014-12-11 9:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 17:04 NULL pointer dereference in i2c-hid Gabriele Mazzotta
2014-12-11 8:58 ` Mika Westerberg [this message]
2014-12-11 14:03 ` Mika Westerberg
2014-12-11 18:16 ` Gabriele Mazzotta
2014-12-11 18:40 ` Andrew Duggan
2014-12-11 19:11 ` Gabriele Mazzotta
2014-12-11 19:21 ` Andrew Duggan
2014-12-11 19:40 ` Gabriele Mazzotta
2014-12-11 20:46 ` Andrew Duggan
2014-12-11 21:17 ` Gabriele Mazzotta
2014-12-11 21:34 ` Andrew Duggan
2014-12-11 21:57 ` Gabriele Mazzotta
2014-12-12 0:26 ` Andrew Duggan
2014-12-12 8:12 ` Gabriele Mazzotta
2014-12-12 19:12 ` Andrew Duggan
2014-12-24 23:53 ` Gabriele Mazzotta
2015-01-08 23:58 ` Andrew Duggan
2015-01-09 8:04 ` Gabriele Mazzotta
2015-01-10 0:29 ` Andrew Duggan
2015-01-10 1:18 ` Gabriele Mazzotta
2015-02-22 21:37 ` Gabriele Mazzotta
2015-02-24 0:30 ` Andrew Duggan
2014-12-11 18:41 ` Benjamin Tissoires
2014-12-11 19:25 ` Gabriele Mazzotta
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=20141211085801.GR1300@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=gabriele.mzt@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).