Re: [PATCH] fbdev: Statically link the framebuffer notification functions

Jon Smirl wrote:
> On 7/11/06, Antonino A. Daplas <[email protected]> wrote:
>> > The code looks ok but this sure smells like inter_module_*.
>>
>> I assure you, there is no smell of inter_module_* here. What scenario
>> are you afraid of?
> 
> Dangling references during the load/unload process. That was
> inter_module's problem.

That won't happen. If fbdev unloads, then the module that does the
notification disappears, and the clients won't receive notifications.
If the client is the one that unloads first, it unregisters its notifier
block, and that's one less client for fbdev to notify (And fbdev doesn't
know how many clients are there, that's internal to the notifier). And
since registration, unregistration and the call to the callout function
in the notifier block are protected by a semaphore (in the blocking type),
the danger of unregistration while in the midst of a notification is
removed.

Tony
-
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/

---

• References:
  • Depmod errors on 2.6.17.4/2.6.18-rc1/2.6.18-rc1-mm1
    • From: Matt Reuther <[email protected]>
  • [PATCH] backlight: lcd: Remove dependency from the framebuffer layer
    • From: "Antonino A. Daplas" <[email protected]>
  • Re: [PATCH] backlight: lcd: Remove dependency from the framebuffer layer
    • From: Andrew Morton <[email protected]>
  • [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Antonino A. Daplas" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Jon Smirl" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Antonino A. Daplas" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Jon Smirl" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Antonino A. Daplas" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Jon Smirl" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Antonino A. Daplas" <[email protected]>
  • Re: [PATCH] fbdev: Statically link the framebuffer notification functions
    • From: "Jon Smirl" <[email protected]>

• Prev by Date: [ patch -mm1 00/02 ] scx200_gpio: use 1 cdev for N minors, not N for N
• Next by Date: [PATCH] x86: Don't randomize stack unless current->personality permits it
• Previous by thread: Re: [PATCH] fbdev: Statically link the framebuffer notification functions
• Next by thread: [PATCH] sound-miro unknown symbols (Depmod errors on 2.6.17.4/2.6.18-rc1/2.6.18-rc1-mm1)
• 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]