unix_diag: Unix inode info NLA

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>

1 files changed, 7 insertions, 0 deletions

diff --git a/include/linux/unix_diag.h b/include/linux/unix_diag.h
index cc4df34d4c14..3e53adbe9c7f 100644
--- a/include/linux/unix_diag.h
+++ b/include/linux/unix_diag.h
@@ -12,6 +12,7 @@ struct unix_diag_req {
 };
 
 #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;
@@ -25,8 +26,14 @@ struct unix_diag_msg {
 
 enum {
         UNIX_DIAG_NAME,
+        UNIX_DIAG_VFS,
 
         UNIX_DIAG_MAX,
 };
 
+struct unix_diag_vfs {
+        __u32   udiag_vfs_ino;
+        __u32   udiag_vfs_dev;
+};
+
 #endif