| 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
| ||
|
Date: Wed, 29 Aug 2007 16:18:31 -0300 From: Arnaldo Carvalho de Melo <acme@...stprotocols.net> To: David Miller <davem@...emloft.net> Cc: dlezcano@...ibm.com, netdev@...r.kernel.org, ralf@...ux-mips.org Subject: Re: [patch 0/1][RFC] add a private field to the sock structure Em Wed, Aug 29, 2007 at 11:23:16AM -0700, David Miller escreveu: > From: dlezcano@...ibm.com > Date: Wed, 29 Aug 2007 18:41:14 +0200 > > > When a socket is created it is sometime useful to store a specific information > > for this socket. > > > > This information can be for examples: > > * a creation time > > * a pid > > * a uid/gid > > * a container identifier > > * a pointer to a more specific structure > > * ... > > > > The following patch is a proposition to add a private anonymous pointer > > field to the common part of the sock structure. > > We got rid of the private field a long time ago because not only > is it not needed, it tends to get abused. Nah, it still there, sk_protinfo, its just ax25 that uses it (nudge(Ralf)). How do we state that a struct field is deprecated and will be removed soon(tm)? There is another, sk_user_data, that is used only by the rpc, pppol2tp, iscsi, ncpfs, smbfs and dlm guys, see? We need a deprecate flag for sk_protinfo, if not people will use it! :-) - Arnaldo - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists