Re: [Patch -mm 0/3] RFC: module unloading vs. release function

On 4/16/07, Cornelia Huck <[email protected]> wrote:

Hi,

based on the discussion in "How should an exit routine wait for
release() callbacks?", I've cooked up some patches that make module
unload wait until the last reference for a kobject has been dropped.
This should plug the "release function in already deleted module" race;
however, if the last kobject_put() from the module containing the
release function is not in the module's exit function, there's still a
small window (not sure if and how to plug this).

Unfortunately all this "wait for refcount in module's exit" schemas
lead to the following deadlock:

       rmmod my_module < /path/to/some/file/incrementing/my/refcount

--
Dmitry
-
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 -mm 0/3] RFC: module unloading vs. release function
    • From: Alan Stern <[email protected]>
  • Re: [Patch -mm 0/3] RFC: module unloading vs. release function
    • From: Greg KH <[email protected]>

• References:
  • [Patch -mm 0/3] RFC: module unloading vs. release function
    • From: Cornelia Huck <[email protected]>

• Prev by Date: Re: [PATCH v2] hpet: Enable hidden HPET on NVidia motherboards
• Next by Date: Re: [AppArmor 00/41] AppArmor security module overview
• Previous by thread: [Patch -mm 0/3] RFC: module unloading vs. release function
• Next by thread: Re: [Patch -mm 0/3] RFC: module unloading vs. release function
• 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]