Thread (2 messages) 2 messages, 2 authors, 2010-09-06

Re: HIDDEV: potential NULL dereference

From: Amit Nagal <hidden>
Date: 2010-09-06 05:33:16
Also in: lkml

Possibly related (same subject, not in this thread)

Hi ,

i was one of the users who informed that crash do disappears .

the reality with me is that the probability of occurence of crash
reduces significantly

but on rigourous testing crash resurfaces again .

sorry for wrong reporting .

Regards
Amit Nagal



On Sat, Sep 4, 2010 at 10:09 PM, Chris Ball [off-list ref] wrote:
Hi Jiri,

  > If hid was ever NULL at this phase, the check couldn't improve
  > anything due to hid->driver_data dereference being still before
  > the check. So again my question, how this could change anything?
  >
  > Above that, it just makes the window shorter, but the bug is
  > still there, isn't it? Is the following scenario reasonable?

You're right -- I'd missed the other dereference, sorry.  It's
surprising that we have two reports from users saying that the
patch got rid of a reproducible oops for them.

Dan Carpenter has commented on this too:
  http://www.spinics.net/lists/linux-input/msg10541.html

As he says, it looks like the code's overdue for some real locking.

Thanks,

- Chris.
--
Chris Ball   [off-list ref]
One Laptop Per Child
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help