diff options
| author | Pavel Emelyanov <xemul@parallels.com> | 2011-12-15 02:45:43 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2011-12-16 13:48:28 -0500 |
| commit | 5f7b0569460b7d8d01ca776430a00505a68b7584 (patch) | |
| tree | f67c5033fb1fe17b45e4b45cbbb162428216f37d /fs/romfs | |
| parent | f5248b48a64c221dd6157ab9cbee5a36ee45e6ed (diff) | |
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>
Diffstat (limited to 'fs/romfs')
0 files changed, 0 insertions, 0 deletions