sock_close() couldn't have been called with NULL inode since at least 2.1.early
authorAl Viro <viro@zeniv.linux.org.uk>
Sun, 14 Apr 2013 21:22:17 +0000 (17:22 -0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 29 Apr 2013 19:41:43 +0000 (15:41 -0400)
... if not since 0.99 or so.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
net/socket.c

index 88f759adf3afba28af3b1a694220c18f5e895616..9663df63e3d166534cbfa71099110fbf89f00478 100644 (file)
@@ -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;
 }