linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: wim@djo.tudelft.nl
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: crash by cdc_acm driver in kernels 4.8-rc1/5
Date: Thu, 06 Oct 2016 12:53:30 +0200	[thread overview]
Message-ID: <1475751210.1957.2.camel@suse.com> (raw)
In-Reply-To: <20160929132612.GA7313@djo.tudelft.nl>

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

On Thu, 2016-09-29 at 15:26 +0200, Wim Osterholt wrote:
> On Wed, Sep 28, 2016 at 05:23:30PM +0200, Oliver Neukum wrote:
> > > 
> > > HP src # sync
> > > HP src # [ 3744.914184] BUG: unable to handle kernel NULL pointer dereference at 00000249
> > 
> > The last view lines before that please with the debugging level ramped
> > up to 9 please.
> 
> Recompiled again, double checked if it was really the new module.
> That doesn't seem to make any difference at all.

Hi,

sorry for the delay. Your results are strange and we will have to do it
the hard way. Could you retest with the attached patch applied
in addition to the last patch I sent?
I can see no good reason for a crash where you see a crash, so brute
force is called for.

	Regards
		Oliver


[-- Attachment #2: 0001-CDC-ACM-insanely-paranoid-debugging.patch --]
[-- Type: text/x-patch, Size: 1445 bytes --]

From f9344147b6c75aca8f66b728e92ab854452255ed Mon Sep 17 00:00:00 2001
From: Oliver Neukum <oneukum@suse.com>
Date: Thu, 6 Oct 2016 12:47:15 +0200
Subject: [PATCH] CDC-ACM: insanely paranoid debugging

---
 drivers/usb/class/cdc-acm.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index 283e16e..32625a3 100644
--- a/drivers/usb/class/cdc-acm.c
+++ b/drivers/usb/class/cdc-acm.c
@@ -1319,11 +1319,13 @@ made_compressed_probe:
 	acm = kzalloc(sizeof(struct acm), GFP_KERNEL);
 	if (acm == NULL)
 		goto alloc_fail;
+	dev_dbg(&intf->dev, "descriptor allocated\n");
 
 	minor = acm_alloc_minor(acm);
 	if (minor < 0)
 		goto alloc_fail1;
 
+	dev_dbg(&intf->dev, "minor allocated\n");
 	WARN_ON(!epctrl);
 	ctrlsize = usb_endpoint_maxp(epctrl);
 	WARN_ON(!epread);
@@ -1343,6 +1345,7 @@ made_compressed_probe:
 	acm->ctrlsize = ctrlsize;
 	acm->readsize = readsize;
 	acm->rx_buflimit = num_rx_buf;
+	dev_dbg(&intf->dev, "descriptor initialized\n");
 	INIT_WORK(&acm->work, acm_softint);
 	init_waitqueue_head(&acm->wioctl);
 	spin_lock_init(&acm->write_lock);
@@ -1351,6 +1354,7 @@ made_compressed_probe:
 	acm->is_int_ep = usb_endpoint_xfer_int(epread);
 	if (acm->is_int_ep)
 		acm->bInterval = epread->bInterval;
+	dev_dbg(&intf->dev, "locks and queues initialized\n");
 	tty_port_init(&acm->port);
 	acm->port.ops = &acm_port_ops;
 	init_usb_anchor(&acm->delayed);
-- 
2.6.2


  reply	other threads:[~2016-10-06 10:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 11:58 crash by cdc_acm driver in kernels 4.8-rc1/5 Wim Osterholt
2016-09-08 12:20 ` Oliver Neukum
2016-09-08 12:58   ` Wim Osterholt
2016-09-08 13:05     ` Oliver Neukum
2016-09-08 15:00       ` Wim Osterholt
2016-09-08 16:54       ` Wim Osterholt
2016-09-09 13:24       ` Wim Osterholt
2016-09-12  2:43       ` Wim Osterholt
2016-09-20 13:05         ` Oliver Neukum
2016-09-20 15:45           ` Wim Osterholt
2016-09-21 12:21             ` Oliver Neukum
2016-09-21 16:21               ` Wim Osterholt
2016-09-21 16:41               ` Wim Osterholt
2016-09-22 14:40                 ` Oliver Neukum
2016-09-22 17:56                   ` Wim Osterholt
2016-09-22 19:21                   ` Wim Osterholt
2016-09-23 10:04                   ` Wim Osterholt
2016-09-27 16:34                   ` Wim Osterholt
2016-09-28  9:16                     ` Oliver Neukum
2016-09-28 14:46                       ` Wim Osterholt
2016-09-28 15:08                       ` Wim Osterholt
2016-09-28 15:23                         ` Oliver Neukum
2016-09-29 13:26                           ` Wim Osterholt
2016-10-06 10:53                             ` Oliver Neukum [this message]
2016-10-17 14:10     ` Oliver Neukum
2016-10-17 15:20       ` Wim Osterholt
2016-10-18 12:18         ` Oliver Neukum
2016-10-18 14:51           ` Wim Osterholt
2016-11-05 13:34           ` Wim Osterholt
2016-11-15  0:16           ` Wim Osterholt
2016-11-15 11:07             ` Oliver Neukum
2016-11-15 11:26             ` poma
2016-11-15 13:29               ` Wim Osterholt
2016-11-16 12:34                 ` Oliver Neukum
2016-11-16 15:07                   ` Wim Osterholt
2016-11-17  1:57                     ` Wim Osterholt
2016-11-17  9:14                       ` Wim Osterholt
2016-11-17 16:11                         ` Wim Osterholt
2016-11-21 13:19                           ` Oliver Neukum
2016-11-21 15:58                             ` Wim Osterholt
2016-11-21 20:23                               ` Wim Osterholt
2016-11-21 23:49                                 ` poma
2016-11-22 17:50                               ` Bjørn Mork
2016-11-23  0:48                                 ` Wim Osterholt
2016-11-22 15:38                             ` Wim Osterholt
2016-11-22 18:08                               ` Bjørn Mork
2016-11-23  0:54                                 ` Wim Osterholt
2016-11-23  7:37                                   ` Bjørn Mork
2016-11-23 15:02                                     ` Alan Stern

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=1475751210.1957.2.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=wim@djo.tudelft.nl \
    /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).