Re: [NETLINK] Don't attach callback to a going-away netlink socket

From: Pavel Emelianov <[email protected]>
Date: Wed, 18 Apr 2007 12:16:18 +0400

> The proposal it to make sock_orphan before detaching the callback
> in netlink_release() and to check for the sock to be SOCK_DEAD in
> netlink_dump_start() before setting a new callback.

As discussed in this thread there might be other ways to a
approach this, but this fix is good for now.

Patch applied, thank you.
-
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: [NETLINK] Don't attach callback to a going-away netlink socket
    • From: Herbert Xu <[email protected]>

• References:
  • [NETLINK] Don't attach callback to a going-away netlink socket
    • From: Pavel Emelianov <[email protected]>

• Prev by Date: Re: 2.6.20.6 vanilla does't boot
• Next by Date: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
• Previous by thread: Re: [NETLINK] Don't attach callback to a going-away netlink socket
• Next by thread: Re: [NETLINK] Don't attach callback to a going-away netlink socket
• 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]