Re: [PATCH RFD] alternative kobject release wait mechanism

Tejun Heo wrote:
> Hello, all.
> 
> Agreed with the problem but I'm not very enthusiastic for adding
> kobj->owner.  How about the following?  exit() routines will have to
> do device_unregister_wait() instead of device_unregister().  On return
> from it, it's guaranteed that all references to it are dropped and
> ->release is finished.  The caller is responsible for avoiding
> deadlock, of course.

Oh, one more thing, with proper code audit, we can just make
device_unregister() do the waiting instead of adding separate
device_unregister_wait().  I think that will be a good step toward
immediate-detach driver model.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH RFD] alternative kobject release wait mechanism
    • From: Cornelia Huck <[email protected]>

• References:
  • [Patch -mm 0/3] RFC: module unloading vs. release function
    • From: Cornelia Huck <[email protected]>
  • [PATCH RFD] alternative kobject release wait mechanism
    • From: Tejun Heo <[email protected]>

• Prev by Date: [PATCH] sysctl_panic_on_oom broken
• Next by Date: Re: Major qla2xxx regression on sparc64
• Previous by thread: [PATCH RFD] alternative kobject release wait mechanism
• Next by thread: Re: [PATCH RFD] alternative kobject release wait mechanism
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]