From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, david-b@pacbell.net
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCHlet] 2.5.23 usb, ide
Date: Thu, 20 Jun 2002 20:49:36 +0200 (MEST) [thread overview]
Message-ID: <UTC200206201849.g5KInaK27367.aeb@smtp.cwi.nl> (raw)
From: David Brownell <david-b@pacbell.net>
> Earlier, I reported an oops at shutdown. I just looked at
> what causes the oops and find that the call
> hcd->driver->stop()
> is executed while hcd->driver->stop is NULL.
>
> ...
> USB people may worry whether hcd->driver->stop should
> have been non-NULL.
Not supposed to be possible. All those hc_driver structures
are declared "static const", with non-null stop(). Looks like
something was zeroing some driver's readonly data segment while
it was still in use. (And who knows that else!)
Now wild pointers happen, and it took me some effort a few
weeks ago to catch one. But at first one should look at
simpler explanations.
Now that you tell me that these things are set at initialization
and never changed, the initialization must be wrong. And indeed,
it says "__devexit_p(uhci_stop)" and this yields NULL.
So, my previous stopoops patch can be replaced by
diff -r linux-2.5.23/linux/drivers/usb/host/uhci-hcd.c linux-2.5.23a/linux/drivers/usb/host/uhci-hcd.c
2431c2431
< static void __devexit uhci_stop(struct usb_hcd *hcd)
---
> static void uhci_stop(struct usb_hcd *hcd)
2512c2512
< stop: __devexit_p(uhci_stop),
---
> stop: uhci_stop,
(pasted from another window).
Andries
next prev reply other threads:[~2002-06-20 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 16:16 Andries.Brouwer
2002-06-20 17:07 ` [linux-usb-devel] " David Brownell
2002-06-20 18:49 ` Andries.Brouwer [this message]
2002-06-20 19:40 ` Petr Vandrovec
2002-06-20 22:06 ` Greg KH
2002-06-20 22:05 ` Greg KH
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=UTC200206201849.g5KInaK27367.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®