Commit 0e2bcaae authored by Al Viro's avatar Al Viro

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: default avatarAl Viro <viro@zeniv.linux.org.uk>
parent e53cfda5
...@@ -1173,15 +1173,6 @@ static int sock_mmap(struct file *file, struct vm_area_struct *vma) ...@@ -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) 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)); sock_release(SOCKET_I(inode));
return 0; return 0;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment