On Wednesday 16 March 2005 8:00 am, Alan Stern wrote:
> On Wed, 16 Mar 2005 [EMAIL PROTECTED] wrote:
>
> > The problem is not reference counting the problem is some code in
> > driver/base/bus.c. First I will describe the scenario:
I suppose your theory for why usbnet/cdc doesn't hit this is:
>
On Wed, Mar 16, 2005 at 11:00:02AM -0500, Alan Stern wrote:
> Greg, I've got some pretty good ideas about how to do it. But they're not
> fully developed and I need help settling some issues. What's a good
> mailing list to discuss these things on? LKML?
lkml works for me, just make sure to CC:
On Wed, 16 Mar 2005 [EMAIL PROTECTED] wrote:
> The problem is not reference counting the problem is some code in
> driver/base/bus.c. First I will describe the scenario:
> All is well and we call the driver remove function which calls
> acm_disconnect. acm_disconnect calls usb_driver_release_int
Brian Murphy <[EMAIL PROTECTED]> said:
> Alan Stern wrote:
>
> >On Mon, 14 Mar 2005, Brian Murphy wrote:
> >
> >
> >
> >>This was nice in theory and partially fixes the problem (no more crash)
> >>unfortunately
> >>the module removal hangs if the data interface is attempted to be
> >>removed
On Tue, 15 Mar 2005, Brian Murphy wrote:
> Yes. I'll look at it tomorrow. If you have any ideas about a good place
> to look then
> that might save me some time.
Considering what David Brownell said, I'd start looking in the driver
itself. I usually add printks to display the important refcount
Alan Stern wrote:
On Mon, 14 Mar 2005, Brian Murphy wrote:
This was nice in theory and partially fixes the problem (no more crash)
unfortunately
the module removal hangs if the data interface is attempted to be
removed first.
This seems to be because usb_driver_claim_interface is not the same
On Monday 14 March 2005 7:57 am, Brian Murphy wrote:
> Brian Murphy wrote:
>
> This seems to be because usb_driver_claim_interface is not the same as
> claiming the interface in the probe routine causing the call to
> usb_driver_release_interface to not decrement some reference
> count somewher
Am Montag, 14. März 2005 16:57 schrieb Brian Murphy:
> The best fix I have found so far is to detect if the disconnect function
> is called first
> with the data interface and just return without doing anything, waiting
> to be called
> with the control interface (see attached patch). This fixes
On Mon, 14 Mar 2005, Brian Murphy wrote:
> This was nice in theory and partially fixes the problem (no more crash)
> unfortunately
> the module removal hangs if the data interface is attempted to be
> removed first.
>
> This seems to be because usb_driver_claim_interface is not the same as
> c
Brian Murphy wrote:
Oliver Neukum wrote:
Could you make a single patch for that?
Regards
Oliver
Here are the patches resubmitted with the exporting of symbols split
off to
a seperate patch.
/Brian
Make sure th
Oliver Neukum wrote:
Could you make a single patch for that?
Regards
Oliver
Here are the patches resubmitted with the exporting of symbols split off to
a seperate patch.
/Brian
Make sure the cdc acm driver frees its two interfaces only once independant
of the order they a
11 matches
Mail list logo
