5f7b056946
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 <xemul@parallels.com> Signed-off-by: David S. Miller <davem@davemloft.net>
39 lines
614 B
C
39 lines
614 B
C
#ifndef __UNIX_DIAG_H__
|
|
#define __UNIX_DIAG_H__
|
|
|
|
struct unix_diag_req {
|
|
__u8 sdiag_family;
|
|
__u8 sdiag_protocol;
|
|
__u16 pad;
|
|
__u32 udiag_states;
|
|
__u32 udiag_ino;
|
|
__u32 udiag_show;
|
|
__u32 udiag_cookie[2];
|
|
};
|
|
|
|
#define UDIAG_SHOW_NAME 0x00000001 /* show name (not path) */
|
|
#define UDIAG_SHOW_VFS 0x00000002 /* show VFS inode info */
|
|
|
|
struct unix_diag_msg {
|
|
__u8 udiag_family;
|
|
__u8 udiag_type;
|
|
__u8 udiag_state;
|
|
__u8 pad;
|
|
|
|
__u32 udiag_ino;
|
|
__u32 udiag_cookie[2];
|
|
};
|
|
|
|
enum {
|
|
UNIX_DIAG_NAME,
|
|
UNIX_DIAG_VFS,
|
|
|
|
UNIX_DIAG_MAX,
|
|
};
|
|
|
|
struct unix_diag_vfs {
|
|
__u32 udiag_vfs_ino;
|
|
__u32 udiag_vfs_dev;
|
|
};
|
|
|
|
#endif
|