public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <jhovold@gmail.com>
To: Mike Remski <mremski@mutualink.net>
Cc: Johan Hovold <jhovold@gmail.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: ftdi_sio BUG: NULL pointer dereference
Date: Wed, 4 Jun 2014 18:00:00 +0200	[thread overview]
Message-ID: <20140604160000.GF11160@localhost> (raw)
In-Reply-To: <538F3E3B.5080906@mutualink.net>

On Wed, Jun 04, 2014 at 11:41:47AM -0400, Mike Remski wrote:
> Ok, had a chance to try the cdc-acm;  yes it's the ancient one that is 
> in the base install of CentOS 6.4 (2.6.32-71.29.1 centos patched).  I'm 
> hitting something similar;  I noticed there where a few commits for NULL 
> pointer dereferences in cdc-acm.c.
> 
> I'll poke into this a bit (yes, I know try a newer kernel, etc) and let 
> you know what I find (or perhaps this looks similar to something already 
> seen?).  This device is the same as the original ftdi crash, 1.2 is the 
> same interface with bNumEndpoints == 0.
> 
> Jun  4 11:35:20 nicA91A84 kernel: cdc_acm 5-2:1.2: This device cannot do 
> calls on its own. It is not a modem.
> Jun  4 11:35:20 nicA91A84 kernel: BUG: unable to handle kernel NULL 
> pointer dereference at 00000004
> Jun  4 11:35:20 nicA91A84 kernel: IP: [<f84f9c9e>] 
> acm_probe+0x44e/0x127c [cdc_acm]
> Jun  4 11:35:20 nicA91A84 kernel: *pdpt = 00000000354eb001 *pde = 
> 000000007f003067
> Jun  4 11:35:20 nicA91A84 kernel: Oops: 0000 [#1] SMP
> Jun  4 11:35:20 nicA91A84 kernel: last sysfs file: 
> /sys/devices/pci0000:00/0000:00:1d.0/usb5/5-2/product

Yeah, you really need to update your kernel. You'll definitely need at
least commit 99f347caa456 ("USB: CDC ACM: Fix NULL pointer
dereference").

No more reports until you've tried a recent kernel, ok? ;)

Johan

  reply	other threads:[~2014-06-04 16:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 14:25 ftdi_sio BUG: NULL pointer dereference Mike Remski
2014-06-02 14:33 ` Johan Hovold
2014-06-02 15:16   ` Mike Remski
2014-06-02 15:40     ` Johan Hovold
2014-06-02 16:02       ` Mike Remski
2014-06-02 16:20         ` Johan Hovold
2014-06-02 16:24           ` Mike Remski
2014-06-02 16:49             ` Johan Hovold
2014-06-02 17:11               ` Mike Remski
2014-06-02 17:46                 ` Johan Hovold
2014-06-02 17:50                   ` Mike Remski
2014-06-03 10:17                   ` Mike Remski
2014-06-04 14:19                     ` Johan Hovold
2014-06-04 14:29                       ` Mike Remski
2014-06-04 14:52                         ` Johan Hovold
2014-06-04 14:54                           ` Mike Remski
2014-06-04 14:55                           ` Mike Remski
2014-06-04 15:09                             ` Johan Hovold
2014-06-04 15:12                               ` Mike Remski
2014-06-04 15:41                               ` Mike Remski
2014-06-04 16:00                                 ` Johan Hovold [this message]
2014-06-04 16:13                                   ` Mike Remski
2014-06-04 17:05                                   ` Mike Remski
2014-06-05  7:10                                     ` Johan Hovold
2014-06-02 16:09       ` Mike Remski
2014-06-02 16:23         ` Greg KH
2014-06-02 16:26           ` Mike Remski

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=20140604160000.GF11160@localhost \
    --to=jhovold@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mremski@mutualink.net \
    /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