Fix a leak in socket(2) when we fail to allocate a file descriptor.
authorAl Viro <viro@zeniv.linux.org.uk>
Wed, 10 Jan 2018 23:47:05 +0000 (18:47 -0500)
committerAl Viro <viro@zeniv.linux.org.uk>
Wed, 10 Jan 2018 23:47:05 +0000 (18:47 -0500)
Got broken by "make sock_alloc_file() do sock_release() on failures" -
cleanup after sock_map_fd() failure got pulled all the way into
sock_alloc_file(), but it used to serve the case when sock_map_fd()
failed *before* getting to sock_alloc_file() as well, and that got
lost.  Trivial to fix, fortunately.

Fixes: 8e1611e23579 (make sock_alloc_file() do sock_release() on failures)
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
net/socket.c

index 42d8e9c9ccd5028793ebeb27fb319911a0f4ce35..82433a2200ec01e59170f3cc66ec40d0e31686ee 100644 (file)
@@ -432,8 +432,10 @@ static int sock_map_fd(struct socket *sock, int flags)
 {
        struct file *newfile;
        int fd = get_unused_fd_flags(flags);
-       if (unlikely(fd < 0))
+       if (unlikely(fd < 0)) {
+               sock_release(sock);
                return fd;
+       }
 
        newfile = sock_alloc_file(sock, flags, NULL);
        if (likely(!IS_ERR(newfile))) {