From: Takashi Iwai <tiwai@suse.de>
To: <samu.p.onkalo@nokia.com>
Cc: <akpm@linux-foundation.org>, <Eric.Piel@tremplin-utc.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH resent] lis3: Fix Oops with NULL platform data
Date: Wed, 22 Sep 2010 15:47:07 +0200 [thread overview]
Message-ID: <s5h8w2t99gk.wl%tiwai@suse.de> (raw)
In-Reply-To: <62697B07E9803846BC582181BD6FB6B831300D2218@NOK-EUMSG-02.mgdnok.nokia.com>
At Wed, 22 Sep 2010 13:56:15 +0200,
<samu.p.onkalo@nokia.com> wrote:
>
>
> Hi
>
> >-----Original Message-----
> >From: ext Takashi Iwai [mailto:tiwai@suse.de]
> >Sent: 22 September, 2010 14:34
> >To: Andrew Morton
> >Cc: Onkalo Samu.P (Nokia-MS/Tampere); Éric Piel; linux-
> >kernel@vger.kernel.org
> >Subject: [PATCH resent] lis3: Fix Oops with NULL platform data
> >
> >The recent addition of threaded irq handler causes a NULL dereference
> >when used with hp_accel driver, which has NULL pdata.
> >
> >Cc: <stable@kernel.org>
> >Signed-off-by: Takashi Iwai <tiwai@suse.de>
> >---
> >
> >This should go to 2.6.36 and 2.6.35-stable tree.
> >
> > drivers/hwmon/lis3lv02d.c | 6 ++++--
> > 1 files changed, 4 insertions(+), 2 deletions(-)
> >
> >diff --git a/drivers/hwmon/lis3lv02d.c b/drivers/hwmon/lis3lv02d.c
> >index 5e15967..1c266ec 100644
> >--- a/drivers/hwmon/lis3lv02d.c
> >+++ b/drivers/hwmon/lis3lv02d.c
> >@@ -354,7 +354,8 @@ static irqreturn_t lis302dl_interrupt_thread1_8b(int
> >irq, void *data)
> >
> > struct lis3lv02d *lis3 = data;
> >
> >- if ((lis3->pdata->irq_cfg & LIS3_IRQ1_MASK) == LIS3_IRQ1_CLICK)
> >+ if (lis3->pdata &&
> >+ (lis3->pdata->irq_cfg & LIS3_IRQ1_MASK) == LIS3_IRQ1_CLICK)
> > lis302dl_interrupt_handle_click(lis3);
> > else
> > lis302dl_interrupt_handle_ff_wu(lis3);
> >@@ -367,7 +368,8 @@ static irqreturn_t lis302dl_interrupt_thread2_8b(int
> >irq, void *data)
> >
> > struct lis3lv02d *lis3 = data;
> >
> >- if ((lis3->pdata->irq_cfg & LIS3_IRQ2_MASK) == LIS3_IRQ2_CLICK)
> >+ if (lis3->pdata &&
> >+ (lis3->pdata->irq_cfg & LIS3_IRQ2_MASK) == LIS3_IRQ2_CLICK)
> > lis302dl_interrupt_handle_click(lis3);
> > else
> > lis302dl_interrupt_handle_ff_wu(lis3);
>
> Yes, that will remove the kernel oops definitely, but I'm wondering if
> this thread should be executed at all if there is no pdata available.
We may control the caller of request_threaded_irq(), instead.
The revised patch is below. (With this patch, the patch for the new
LIS3CD chip must be revised, too.)
> Eric, is it so that in laptops interrupts are used for free fall detection
> and polled input device is for joystick?
Yes, it's so for HP laptops.
> Interrupts can (and are used) also for other purposes but in that case
> some additional configurations are done based on platform data.
>
> With this patch, there are just some additional input event refreshes in
> top of polled device updates. It should really not matter. So,
>
> Acked-by: Samu Onkalo <samu.p.onkalo@nokia.com>
>
> -Samu
thanks,
Takashi
===
>From 0e5bdc7516915e92fe471a77da36ecb75d995c0f Mon Sep 17 00:00:00 2001
From: Takashi Iwai <tiwai@suse.de>
Date: Wed, 22 Sep 2010 12:16:04 +0200
Subject: [PATCH] lis3: Fix Oops with NULL platform data
The recent addition of threaded irq handler causes a NULL dereference
when used with hp_accel driver, which has NULL pdata.
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
this version avoids the unnecessary thread_irq call instead of checking
pdata in the irq handler.
drivers/hwmon/lis3lv02d.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hwmon/lis3lv02d.c b/drivers/hwmon/lis3lv02d.c
index 5e15967..0a24177 100644
--- a/drivers/hwmon/lis3lv02d.c
+++ b/drivers/hwmon/lis3lv02d.c
@@ -301,7 +301,7 @@ static irqreturn_t lis302dl_interrupt(int irq, void *dummy)
wake_up_interruptible(&lis3_dev.misc_wait);
kill_fasync(&lis3_dev.async_queue, SIGIO, POLL_IN);
out:
- if (lis3_dev.whoami == WAI_8B && lis3_dev.idev &&
+ if (lis3_dev.pdata && lis3_dev.whoami == WAI_8B && lis3_dev.idev &&
lis3_dev.idev->input->users)
return IRQ_WAKE_THREAD;
return IRQ_HANDLED;
@@ -742,7 +742,7 @@ int lis3lv02d_init_device(struct lis3lv02d *dev)
* io-apic is not configurable (and generates a warning) but I keep it
* in case of support for other hardware.
*/
- if (dev->whoami == WAI_8B)
+ if (dev->pdata && dev->whoami == WAI_8B)
thread_fn = lis302dl_interrupt_thread1_8b;
else
thread_fn = NULL;
--
1.7.2.2
next prev parent reply other threads:[~2010-09-22 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 11:34 Takashi Iwai
2010-09-22 11:37 ` Takashi Iwai
2010-09-22 11:56 ` samu.p.onkalo
2010-09-22 13:47 ` Takashi Iwai [this message]
2010-09-23 5:06 ` samu.p.onkalo
2010-09-23 5:33 ` [lm-sensors] " Guenter Roeck
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=s5h8w2t99gk.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Eric.Piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samu.p.onkalo@nokia.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
all inboxes | Powered by JetHome®