From: Al Viro <viro@zeniv.linux.org.uk>
Date: Sun, 14 Apr 2013 21:22:17 +0000 (-0400)
Subject: sock_close() couldn't have been called with NULL inode since at least 2.1.early
X-Git-Tag: accepted/tizen/common/20141203.182822~2374^2~72
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0e2bcaae836e535236244bfc900626ee541eb7bb;p=platform%2Fkernel%2Flinux-arm64.git

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>
---

diff --git a/net/socket.c b/net/socket.c
index 88f759a..9663df6 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;
 }