diff options
author | Al Viro <viro@zeniv.linux.org.uk> | 2013-04-14 17:22:17 -0400 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2013-04-29 15:41:43 -0400 |
commit | 0e2bcaae836e535236244bfc900626ee541eb7bb (patch) | |
tree | 69b40e8c00807f345943d2f4f949efa00a223629 | |
parent | e53cfda5d2c90a6dd763eb72034c775add729e40 (diff) |
sock_close() couldn't have been called with NULL inode since at least 2.1.early
... if not since 0.99 or so.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
-rw-r--r-- | net/socket.c | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/net/socket.c b/net/socket.c index 88f759adf3af..9663df63e3d1 100644 --- a/net/socket.c +++ b/net/socket.c @@ -1173,15 +1173,6 @@ static int sock_mmap(struct file *file, struct vm_area_struct *vma) static int sock_close(struct inode *inode, struct file *filp) { - /* - * It was possible the inode is NULL we were - * closing an unfinished socket. - */ - - if (!inode) { - printk(KERN_DEBUG "sock_close: NULL inode\n"); - return 0; - } sock_release(SOCKET_I(inode)); return 0; } |