Re: Kernelnewbies Digest, Vol 37, Issue 37

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



unsubscribe


On Sat, Dec 28, 2013 at 12:00 PM, <kernelnewbies-request@xxxxxxxxxxxxxxxxx> wrote:
Send Kernelnewbies mailing list submissions to
        kernelnewbies@xxxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
        kernelnewbies-request@xxxxxxxxxxxxxxxxx

You can reach the person managing the list at
        kernelnewbies-owner@xxxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kernelnewbies digest..."


Today's Topics:

   1. Re: Can't cleanly unload driver (Valdis.Kletnieks@xxxxxx)


----------------------------------------------------------------------

Message: 1
Date: Sat, 28 Dec 2013 00:13:08 -0500
From: Valdis.Kletnieks@xxxxxx
Subject: Re: Can't cleanly unload driver
To: Eric Fowler <eric.fowler@xxxxxxxxx>
Cc: kernelnewbies@xxxxxxxxxxxxxxxxx
Message-ID: <221197.1388207588@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

On Fri, 27 Dec 2013 19:33:50 -0800, Eric Fowler said:

> I suspect I am doing something wrong in the code with
> register/unregister_chrdev(), but I have been over that code a million
> times. It looks fine.
>
> Now:
> insmod the device, OK
> rmmod the device, OK
> Check /proc/devices , device # is present
> insmod the device again, fails with ERROR: could not insert module
> ./foobar.ko: Device or resource busy

It does smell like an unregister issue.  You may want to try adding
printk() calls to print out the return code from register and unregister.
I'm willing to bet that (a) the unegister is failing because somebody
still has a reference on the device, and (b) the second register call fails
because the device already exists, causing your module_init() to bail out.

The fun is that you may not have taken a reference on the device directly
yourself - you may have called some other get_foo() that ends up taking an
implicit reference under the covers, causing issues when you fail to call
put_foo() at the right place...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131228/292e4d34/attachment-0001.bin

------------------------------

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


End of Kernelnewbies Digest, Vol 37, Issue 37
*********************************************

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux