netdev - Re: [RFC] netlink: add socket destruction notification

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1257788771.29454.191.camel@johannes.local>
Date:	Mon, 09 Nov 2009 18:46:11 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	netdev <netdev@...r.kernel.org>, Jouni Malinen <j@...fi>,
	Thomas Graf <tgraf@...g.ch>
Subject: Re: [RFC] netlink: add socket destruction notification

On Mon, 2009-11-09 at 17:57 +0100, Patrick McHardy wrote:

> > Oh? So on which sockets can I rely on it being used? After sending at
> > least one unicast message into the kernel? This seems to depend on pid
> > being assigned -- when is that?
> 
> All unicast sockets that have either manually or automatically
> bound. Automatic binding happens when sending the first message
> or when calling connect().
> 
> Before that, your code can't know of the sockets existance, so
> I guess this should be fine.

Ah, yes, of course... that's part of the boilerplate code to use generic
netlink so I always forget about what exactly is going on there :)

Thanks!

johannes


Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)