netdev - Re: [patch 0/1][RFC] add a private field to the sock structure

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070829.112316.98862875.davem@davemloft.net>
Date:	Wed, 29 Aug 2007 11:23:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dlezcano@...ibm.com
Cc:	netdev@...r.kernel.org
Subject: Re: [patch 0/1][RFC] add a private field to the sock structure

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.

Find another way to implement your feature.
-
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