Re: kldunload DIAGNOSTIC idea...

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 07/21/04

  • Next message: Poul-Henning Kamp: "Re: kldunload DIAGNOSTIC idea..."
    To: Doug Rabson <dfr@nlsystems.com>
    Date: Wed, 21 Jul 2004 11:21:39 +0200
    
    

    In message <200407211010.08159.dfr@nlsystems.com>, Doug Rabson writes:

    >The original intention was that drivers use the
    >device_busy()/device_unbusy() counter to handle these things. In some
    >cases, just calling device_busy() from fooopen() and device_unbusy()
    >from fooclose() is sufficient.

    That is not enough. All methods in cdevsw, and things not in cdevsw
    (clone handlers, call backs, etc etc) needs to refcount.

    I have a lot of this working in a tree here, and will commit it once
    I have gone over it a few more times.

    -- 
    Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
    phk@FreeBSD.ORG         | TCP/IP since RFC 956
    FreeBSD committer       | BSD since 4.3-tahoe    
    Never attribute to malice what can adequately be explained by incompetence.
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
    

  • Next message: Poul-Henning Kamp: "Re: kldunload DIAGNOSTIC idea..."