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

Pavel Emelianov wrote:
> From: Denis Lunev <[email protected]>
> 
> There is a race between netlink_dump_start() and netlink_release()
> that can lead to the situation when a netlink socket with non-zero
> callback is freed.


Can you describe the race in more detail please?

-
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] Don't attach callback to a going-away netlink socket
  - From: Pavel Emelianov <[email protected]>

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

Prev by Date: Re: [BUG] 2.6.21-rc7 hpt366 driver broken
Next by Date: Re: [PATCH -mm] scheduler: fix the return of the first time_slice
Previous by thread: [PATCH] Don't attach callback to a going-away netlink socket
Next by thread: Re: [PATCH] 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]