kernel - saturneric's kernel source tree

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	unix_diag: Unix inode info NLA	Pavel Emelyanov	2011-12-16	1	-0/+21
\| \| \| \| \| \| \| \| \| \| \| \| \|	Actually, the socket path if it's not anonymous doesn't give a clue to which file the socket is bound to. Even if the path is absolute, it can be unlinked and then new socket can be bound to it. With this NLA it's possible to check which file a particular socket is really bound to. Signed-off-by: Pavel Emelyanov <[email protected]> Signed-off-by: David S. Miller <[email protected]>
*	unix_diag: Unix socket name NLA	Pavel Emelyanov	2011-12-16	1	-0/+20
\| \| \| \| \| \| \| \|	Report the sun_path when requested as NLA. With leading '\0' if present but without the leading AF_UNIX bits. Signed-off-by: Pavel Emelyanov <[email protected]> Signed-off-by: David S. Miller <[email protected]>
*	unix_diag: Dumping exact socket core	Pavel Emelyanov	2011-12-16	1	-1/+66
\| \| \| \| \| \| \| \| \| \| \| \|	The socket inode is used as a key for lookup. This is effectively the only really unique ID of a unix socket, but using this for search currently has one problem -- it is O(number of sockets) :( Does it worth fixing this lookup or inventing some other ID for unix sockets? Signed-off-by: Pavel Emelyanov <[email protected]> Signed-off-by: David S. Miller <[email protected]>
*	unix_diag: Dumping all sockets core	Pavel Emelyanov	2011-12-16	1	-1/+75
\| \| \| \| \| \| \| \|	Walk the unix sockets table and fill the core response structure, which includes type, state and inode. Signed-off-by: Pavel Emelyanov <[email protected]> Signed-off-by: David S. Miller <[email protected]>
*	unix_diag: Basic module skeleton	Pavel Emelyanov	2011-12-16	1	-0/+57
	Includes basic module_init/_exit functionality, dump/get_exact stubs and declares the basic API structures for request and response. Signed-off-by: Pavel Emelyanov <[email protected]> Signed-off-by: David S. Miller <[email protected]>