Skip to contentSkip to conversation

sock_alloc_file() cleanups and fixes

RFC PATCH In review Al Viro 4 participants 12 messages Dec 1, 2017 – Dec 5, 2017

Subsystems (6)
lore
Share & tools
lore

Al Viro

author
#0 lore raw

RFC PATCH 1/1 sock_alloc_file() cleanups and fixes

Almost all sock_alloc_file() callers want sock_release()
in case of failure. Currently it consumes socket on success (it will be destroyed on final fput() of resulting file) and leaves it alone on failure. Making it consume socket in all cases makes for simpler life in callers.

There are 3 exceptions:

* sock_map_fd() calls sock_alloc_file(), but doesn't do sock_release() in case of failure. Its caller (sys_socket()) does, though, and it does get considerably simpler with sock_alloc_file() doing the cleanup in case of failure.

* sys_socketpair(). Handling of sock_alloc_file() failures is complicated by attempts to share bits and pieces of failure exits between various points of failure in there. Reordering things a bit (reserving descriptors and copying them to userland before doing anything else) makes for simpler handling of failure exits and after such massage we get the situation when failure of sock_alloc_file() is immediately followed by sock_release().

* kcm_clone(). Badly broken in several respects - sk_alloc() failure ends up with double-free of struct socket (we do fput(), then sock_release()) and copy_to_user() failure uses sys_close() to undo fd_install(), which is something we should never do. Descriptor table might be shared and fd_install() should only be done past the last possible failure point. Fixing all of that is simple - we just need to move allocation of descriptor and fd_install() into the caller (before and after the call of kcm_clone(), resp.) and untangle the failure exits. Makes for much simpler calling conventions for kcm_clone(), while we are at it, and as a side effect we get "sock_release() in case of sock_alloc_file() failure" for that one as well.

The patch series (in followups to this mail and in
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git#work.net) does the following:
1) massage sys_socketpair() (should be a pure cleanup)
2) fix and clean up kcm_clone() (-stable fodder)
3) switch sock_alloc_file() to new calling conventions.

It got some local testing, but it certainly needs more review.
Diffstat for the entire thing is

 drivers/staging/lustre/lnet/lnet/lib-socket.c |   8 ++---
 net/9p/trans_fd.c                             |   1 -
 net/kcm/kcmsock.c                             |  68 ++++++++++++++---------------------------
 net/sctp/socket.c                             |   1 -
 net/socket.c                                  | 110 +++++++++++++++++++++++++++----------------------------------------
 5 files changed, 69 insertions(+), 119 deletions(-)

Please, review and comment.

author
#1 lore raw

PATCH 1/3 socketpair(): allocate descriptors first

simplifies failure exits considerably...

---
 net/socket.c | 89 ++++++++++++++++++++++++++----------------------------------
 1 file changed, 38 insertions(+), 51 deletions(-)
net/socket.c +38 -51
index 42d8e9c9ccd5..2df83c0bfde9 100644
@@ -1366,87 +1366,74 @@ SYSCALL_DEFINE4(socketpair, int, family, int, type, int, protocol,
 		flags = (flags & ~SOCK_NONBLOCK) | O_NONBLOCK;
 
 	/*
+	 * reserve descriptors and make sure we won't fail
+	 * to return them to userland.
+	 */
+	fd1 = get_unused_fd_flags(flags);
+	if (unlikely(fd1 < 0))
+		return fd1;
+
+	fd2 = get_unused_fd_flags(flags);
+	if (unlikely(fd2 < 0)) {
+		put_unused_fd(fd1);
+		return fd2;
+	}
+
+	err = put_user(fd1, &usockvec[0]);
+	if (err)
+		goto out;
+
+	err = put_user(fd2, &usockvec[1]);
+	if (err)
+		goto out;
+
+	/*
 	 * Obtain the first socket and check if the underlying protocol
 	 * supports the socketpair call.
 	 */
 
 	err = sock_create(family, type, protocol, &sock1);
-	if (err < 0)
+	if (unlikely(err < 0))
 		goto out;
 
 	err = sock_create(family, type, protocol, &sock2);
-	if (err < 0)
-		goto out_release_1;
-
-	err = sock1->ops->socketpair(sock1, sock2);
-	if (err < 0)
-		goto out_release_both;
-
-	fd1 = get_unused_fd_flags(flags);
-	if (unlikely(fd1 < 0)) {
-		err = fd1;
-		goto out_release_both;
+	if (unlikely(err < 0)) {
+		sock_release(sock1);
+		goto out;
 	}
 
-	fd2 = get_unused_fd_flags(flags);
-	if (unlikely(fd2 < 0)) {
-		err = fd2;
-		goto out_put_unused_1;
+	err = sock1->ops->socketpair(sock1, sock2);
+	if (unlikely(err < 0)) {
+		sock_release(sock2);
+		sock_release(sock1);
+		goto out;
 	}
 
 	newfile1 = sock_alloc_file(sock1, flags, NULL);
 	if (IS_ERR(newfile1)) {
 		err = PTR_ERR(newfile1);
-		goto out_put_unused_both;
+		sock_release(sock1);
+		sock_release(sock2);
+		goto out;
 	}
 
 	newfile2 = sock_alloc_file(sock2, flags, NULL);
 	if (IS_ERR(newfile2)) {
 		err = PTR_ERR(newfile2);
-		goto out_fput_1;
+		sock_release(sock2);
+		fput(newfile1);
+		goto out;
 	}
 
-	err = put_user(fd1, &usockvec[0]);
-	if (err)
-		goto out_fput_both;
-
-	err = put_user(fd2, &usockvec[1]);
-	if (err)
-		goto out_fput_both;
-
 	audit_fd_pair(fd1, fd2);
 
 	fd_install(fd1, newfile1);
 	fd_install(fd2, newfile2);
-	/* fd1 and fd2 may be already another descriptors.
-	 * Not kernel problem.
-	 */
-
 	return 0;
 
-out_fput_both:
-	fput(newfile2);
-	fput(newfile1);
-	put_unused_fd(fd2);
-	put_unused_fd(fd1);
-	goto out;
-
-out_fput_1:
-	fput(newfile1);
-	put_unused_fd(fd2);
-	put_unused_fd(fd1);
-	sock_release(sock2);
-	goto out;
-
-out_put_unused_both:
+out:
 	put_unused_fd(fd2);
-out_put_unused_1:
 	put_unused_fd(fd1);
-out_release_both:
-	sock_release(sock2);
-out_release_1:
-	sock_release(sock1);
-out:
 	return err;
 }
 
Signature · 1 line
2.11.0
author
#3 lore raw

PATCH 2/3 fix kcm_clone()

In reply to Al Viro

1) it's fput() or sock_release(), not both
2) don't do fd_install() until the last failure exit.
3) not a bug per se, but... don't attach socket to struct file until it's set up.

Take reserving descriptor into the caller, move fd_install() to the caller, sanitize failure exits and calling conventions.

---
 net/kcm/kcmsock.c | 71 +++++++++++++++++++++----------------------------------
 1 file changed, 27 insertions(+), 44 deletions(-)
net/kcm/kcmsock.c +27 -44
index 0b750a22c4b9..c5fa634e63ca 100644
@@ -1625,60 +1625,35 @@ static struct proto kcm_proto = {
 };
 
 /* Clone a kcm socket. */
-static int kcm_clone(struct socket *osock, struct kcm_clone *info,
-		     struct socket **newsockp)
+static struct file *kcm_clone(struct socket *osock)
 {
 	struct socket *newsock;
 	struct sock *newsk;
-	struct file *newfile;
-	int err, newfd;
+	struct file *file;
 
-	err = -ENFILE;
 	newsock = sock_alloc();
 	if (!newsock)
-		goto out;
+		return ERR_PTR(-ENFILE);
 
 	newsock->type = osock->type;
 	newsock->ops = osock->ops;
 
 	__module_get(newsock->ops->owner);
 
-	newfd = get_unused_fd_flags(0);
-	if (unlikely(newfd < 0)) {
-		err = newfd;
-		goto out_fd_fail;
-	}
-
-	newfile = sock_alloc_file(newsock, 0, osock->sk->sk_prot_creator->name);
-	if (IS_ERR(newfile)) {
-		err = PTR_ERR(newfile);
-		goto out_sock_alloc_fail;
-	}
-
 	newsk = sk_alloc(sock_net(osock->sk), PF_KCM, GFP_KERNEL,
 			 &kcm_proto, true);
 	if (!newsk) {
-		err = -ENOMEM;
-		goto out_sk_alloc_fail;
+		sock_release(newsock);
+		return ERR_PTR(-ENOMEM);
 	}
-
 	sock_init_data(newsock, newsk);
 	init_kcm_sock(kcm_sk(newsk), kcm_sk(osock->sk)->mux);
 
-	fd_install(newfd, newfile);
-	*newsockp = newsock;
-	info->fd = newfd;
-
-	return 0;
+	file = sock_alloc_file(newsock, 0, osock->sk->sk_prot_creator->name);
+	if (IS_ERR(file))
+		sock_release(newsock);
 
-out_sk_alloc_fail:
-	fput(newfile);
-out_sock_alloc_fail:
-	put_unused_fd(newfd);
-out_fd_fail:
-	sock_release(newsock);
-out:
-	return err;
+	return file;
 }
 
 static int kcm_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
@@ -1708,17 +1683,25 @@ static int kcm_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
 	}
 	case SIOCKCMCLONE: {
 		struct kcm_clone info;
-		struct socket *newsock = NULL;
-
-		err = kcm_clone(sock, &info, &newsock);
-		if (!err) {
-			if (copy_to_user((void __user *)arg, &info,
-					 sizeof(info))) {
-				err = -EFAULT;
-				sys_close(info.fd);
-			}
-		}
+		struct file *file;
+
+		info.fd = get_unused_fd_flags(0);
+		if (unlikely(info.fd < 0))
+			return info.fd;
 
+		file = kcm_clone(sock);
+		if (IS_ERR(file)) {
+			put_unused_fd(info.fd);
+			return PTR_ERR(file);
+		}
+		if (copy_to_user((void __user *)arg, &info,
+				 sizeof(info))) {
+			put_unused_fd(info.fd);
+			fput(file);
+			return -EFAULT;
+		}
+		fd_install(info.fd, file);
+		err = 0;
 		break;
 	}
 	default:
Signature · 1 line
2.11.0
#4 lore raw

Re: [PATCH 2/3] fix kcm_clone()

Sorry for top posting.

Lets CC Tom on this patch ?

Quoted 128 lines · Al Viro

1) it's fput() or sock_release(), not both
2) don't do fd_install() until the last failure exit.
3) not a bug per se, but... don't attach socket to struct file until it's set up.

Take reserving descriptor into the caller, move fd_install() to the caller, sanitize failure exits and calling conventions.

---
 net/kcm/kcmsock.c | 71 +++++++++++++++++++++----------------------
------------

 1 file changed, 27 insertions(+), 44 deletions(-)
net/kcm/kcmsock.c +0 -0
index 0b750a22c4b9..c5fa634e63ca 100644
@@ -1625,60 +1625,35 @@ static struct proto kcm_proto = {
  };


 /* Clone a kcm socket. */

net/kcm/kcmsock.c +1 -2
-static int kcm_clone(struct socket *osock, struct kcm_clone *info,
-		     struct socket **newsockp)
+static struct file *kcm_clone(struct socket *osock)

 {
  struct socket *newsock;
  struct sock *newsk;

net/kcm/kcmsock.c +1 -2
-	struct file *newfile;
-	int err, newfd;
+	struct file *file;

net/kcm/kcmsock.c +0 -1
-	err = -ENFILE;

  newsock = sock_alloc();
  if (!newsock)

net/kcm/kcmsock.c +1 -1
-		goto out;
+		return ERR_PTR(-ENFILE);


  newsock->type = osock->type;
  newsock->ops = osock->ops;

  __module_get(newsock->ops->owner);

net/kcm/kcmsock.c +0 -7
-	newfd = get_unused_fd_flags(0);
-	if (unlikely(newfd < 0)) {
-		err = newfd;
-		goto out_fd_fail;
-	}
-
-	newfile = sock_alloc_file(newsock, 0, osock->sk-
Quoted 1 line

sk_prot_creator->name);

net/kcm/kcmsock.c +0 -5
-	if (IS_ERR(newfile)) {
-		err = PTR_ERR(newfile);
-		goto out_sock_alloc_fail;
-	}
-

  newsk = sk_alloc(sock_net(osock->sk), PF_KCM, GFP_KERNEL, &kcm_proto, true);
  if (!newsk) {

net/kcm/kcmsock.c +2 -2
-		err = -ENOMEM;
-		goto out_sk_alloc_fail;
+		sock_release(newsock);
+		return ERR_PTR(-ENOMEM);

  }
-
  sock_init_data(newsock, newsk); init_kcm_sock(kcm_sk(newsk), kcm_sk(osock->sk)->mux);

net/kcm/kcmsock.c +1 -5
-	fd_install(newfd, newfile);
-	*newsockp = newsock;
-	info->fd = newfd;
-
-	return 0;
+	file = sock_alloc_file(newsock, 0, osock->sk-
Quoted 1 line

sk_prot_creator->name);

net/kcm/kcmsock.c +2 -0
+	if (IS_ERR(file))
+		sock_release(newsock);

net/kcm/kcmsock.c +1 -8
-out_sk_alloc_fail:
-	fput(newfile);
-out_sock_alloc_fail:
-	put_unused_fd(newfd);
-out_fd_fail:
-	sock_release(newsock);
-out:
-	return err;
+	return file;

 }

 static int kcm_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)

net/kcm/kcmsock.c +5 -10
@@ -1708,17 +1683,25 @@ static int kcm_ioctl(struct socket *sock,
 unsigned int cmd, unsigned long arg)
  	}
  	case SIOCKCMCLONE: {
  		struct kcm_clone info;
-		struct socket *newsock = NULL;
-
-		err = kcm_clone(sock, &info, &newsock);
-		if (!err) {
-			if (copy_to_user((void __user *)arg, &info,
-					 sizeof(info))) {
-				err = -EFAULT;
-				sys_close(info.fd);
-			}
-		}
+		struct file *file;
+
+		info.fd = get_unused_fd_flags(0);
+		if (unlikely(info.fd < 0))
+			return info.fd;

net/kcm/kcmsock.c +13 -0
+		file = kcm_clone(sock);
+		if (IS_ERR(file)) {
+			put_unused_fd(info.fd);
+			return PTR_ERR(file);
+		}
+		if (copy_to_user((void __user *)arg, &info,
+				 sizeof(info))) {
+			put_unused_fd(info.fd);
+			fput(file);
+			return -EFAULT;
+		}
+		fd_install(info.fd, file);
+		err = 0;

  break;
  }
  default:

Acked-by on v1 2/3
#5 lore raw

Re: [PATCH 2/3] fix kcm_clone()

In reply to Al Viro
Quoted 9 lines · Al Viro

1) it's fput() or sock_release(), not both
2) don't do fd_install() until the last failure exit.
3) not a bug per se, but... don't attach socket to struct file until it's set up.

Take reserving descriptor into the caller, move fd_install() to the caller, sanitize failure exits and calling conventions.

Thanks for the fix! I'll try to test some today also.

Quoted 117 lines
---
 net/kcm/kcmsock.c | 71 +++++++++++++++++++++----------------------------------
 1 file changed, 27 insertions(+), 44 deletions(-)
net/kcm/kcmsock.c +27 -45
index 0b750a22c4b9..c5fa634e63ca 100644
@@ -1625,60 +1625,35 @@ static struct proto kcm_proto = {
 };
 
 /* Clone a kcm socket. */
-static int kcm_clone(struct socket *osock, struct kcm_clone *info,
-                    struct socket **newsockp)
+static struct file *kcm_clone(struct socket *osock)
 {
        struct socket *newsock;
        struct sock *newsk;
-       struct file *newfile;
-       int err, newfd;
+       struct file *file;
 
-       err = -ENFILE;
        newsock = sock_alloc();
        if (!newsock)
-               goto out;
+               return ERR_PTR(-ENFILE);
 
        newsock->type = osock->type;
        newsock->ops = osock->ops;
 
        __module_get(newsock->ops->owner);
 
-       newfd = get_unused_fd_flags(0);
-       if (unlikely(newfd < 0)) {
-               err = newfd;
-               goto out_fd_fail;
-       }
-
-       newfile = sock_alloc_file(newsock, 0, osock->sk->sk_prot_creator->name);
-       if (IS_ERR(newfile)) {
-               err = PTR_ERR(newfile);
-               goto out_sock_alloc_fail;
-       }
-
        newsk = sk_alloc(sock_net(osock->sk), PF_KCM, GFP_KERNEL,
                         &kcm_proto, true);
        if (!newsk) {
-               err = -ENOMEM;
-               goto out_sk_alloc_fail;
+               sock_release(newsock);
+               return ERR_PTR(-ENOMEM);
        }
-
        sock_init_data(newsock, newsk);
        init_kcm_sock(kcm_sk(newsk), kcm_sk(osock->sk)->mux);
 
-       fd_install(newfd, newfile);
-       *newsockp = newsock;
-       info->fd = newfd;
-
-       return 0;
+       file = sock_alloc_file(newsock, 0, osock->sk->sk_prot_creator->name);
+       if (IS_ERR(file))
+               sock_release(newsock);
 
-out_sk_alloc_fail:
-       fput(newfile);
-out_sock_alloc_fail:
-       put_unused_fd(newfd);
-out_fd_fail:
-       sock_release(newsock);
-out:
-       return err;
+       return file;
 }
 
 static int kcm_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
@@ -1708,17 +1683,25 @@ static int kcm_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
        }
        case SIOCKCMCLONE: {
                struct kcm_clone info;
-               struct socket *newsock = NULL;
-
-               err = kcm_clone(sock, &info, &newsock);
-               if (!err) {
-                       if (copy_to_user((void __user *)arg, &info,
-                                        sizeof(info))) {
-                               err = -EFAULT;
-                               sys_close(info.fd);
-                       }
-               }
+               struct file *file;
+
+               info.fd = get_unused_fd_flags(0);
+               if (unlikely(info.fd < 0))
+                       return info.fd;
 
+               file = kcm_clone(sock);
+               if (IS_ERR(file)) {
+                       put_unused_fd(info.fd);
+                       return PTR_ERR(file);
+               }
+               if (copy_to_user((void __user *)arg, &info,
+                                sizeof(info))) {
+                       put_unused_fd(info.fd);
+                       fput(file);
+                       return -EFAULT;
+               }
+               fd_install(info.fd, file);
+               err = 0;
                break;
        }
        default:
--

2.11.0

author
#6 lore raw

PATCH 3/3 make sock_alloc_file() do sock_release() on failures

In reply to Al Viro

This changes calling conventions (and simplifies the hell out the callers). New rules: once struct socket had been passed to sock_alloc_file(), it's been consumed either by struct file or by sock_release() done by sock_alloc_file(). Either way the caller should not do sock_release() after that point.

---
 drivers/staging/lustre/lnet/lnet/lib-socket.c |  8 ++------
 net/9p/trans_fd.c                             |  1 -
 net/kcm/kcmsock.c                             |  7 +------
 net/sctp/socket.c                             |  1 -
 net/socket.c                                  | 25 ++++++++-----------------
 5 files changed, 11 insertions(+), 31 deletions(-)
drivers/staging/lustre/lnet/lnet/lib-socket.c +2 -6
index 539a26444f31..7d49d4865298 100644
@@ -71,16 +71,12 @@ lnet_sock_ioctl(int cmd, unsigned long arg)
 	}
 
 	sock_filp = sock_alloc_file(sock, 0, NULL);
-	if (IS_ERR(sock_filp)) {
-		sock_release(sock);
-		rc = PTR_ERR(sock_filp);
-		goto out;
-	}
+	if (IS_ERR(sock_filp))
+		return PTR_ERR(sock_filp);
 
 	rc = kernel_sock_unlocked_ioctl(sock_filp, cmd, arg);
 
 	fput(sock_filp);
-out:
 	return rc;
 }
 
net/9p/trans_fd.c +0 -1
index 985046ae4231..80f5c79053a4 100644
@@ -839,7 +839,6 @@ static int p9_socket_open(struct p9_client *client, struct socket *csocket)
 	if (IS_ERR(file)) {
 		pr_err("%s (%d): failed to map fd\n",
 		       __func__, task_pid_nr(current));
-		sock_release(csocket);
 		kfree(p);
 		return PTR_ERR(file);
 	}
net/kcm/kcmsock.c +1 -6
index c5fa634e63ca..d4e98f20fc2a 100644
@@ -1629,7 +1629,6 @@ static struct file *kcm_clone(struct socket *osock)
 {
 	struct socket *newsock;
 	struct sock *newsk;
-	struct file *file;
 
 	newsock = sock_alloc();
 	if (!newsock)
@@ -1649,11 +1648,7 @@ static struct file *kcm_clone(struct socket *osock)
 	sock_init_data(newsock, newsk);
 	init_kcm_sock(kcm_sk(newsk), kcm_sk(osock->sk)->mux);
 
-	file = sock_alloc_file(newsock, 0, osock->sk->sk_prot_creator->name);
-	if (IS_ERR(file))
-		sock_release(newsock);
-
-	return file;
+	return sock_alloc_file(newsock, 0, osock->sk->sk_prot_creator->name);
 }
 
 static int kcm_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
net/sctp/socket.c +0 -1
index 3204a9b29407..8bb5163d6331 100644
@@ -5080,7 +5080,6 @@ static int sctp_getsockopt_peeloff_common(struct sock *sk, sctp_peeloff_arg_t *p
 	*newfile = sock_alloc_file(newsock, 0, NULL);
 	if (IS_ERR(*newfile)) {
 		put_unused_fd(retval);
-		sock_release(newsock);
 		retval = PTR_ERR(*newfile);
 		*newfile = NULL;
 		return retval;
net/socket.c +8 -17
index 2df83c0bfde9..05f361faec45 100644
@@ -406,8 +406,10 @@ struct file *sock_alloc_file(struct socket *sock, int flags, const char *dname)
 		name.len = strlen(name.name);
 	}
 	path.dentry = d_alloc_pseudo(sock_mnt->mnt_sb, &name);
-	if (unlikely(!path.dentry))
+	if (unlikely(!path.dentry)) {
+		sock_release(sock);
 		return ERR_PTR(-ENOMEM);
+	}
 	path.mnt = mntget(sock_mnt);
 
 	d_instantiate(path.dentry, SOCK_INODE(sock));
@@ -415,9 +417,11 @@ struct file *sock_alloc_file(struct socket *sock, int flags, const char *dname)
 	file = alloc_file(&path, FMODE_READ | FMODE_WRITE,
 		  &socket_file_ops);
 	if (IS_ERR(file)) {
-		/* drop dentry, keep inode */
+		/* drop dentry, keep inode for a bit */
 		ihold(d_inode(path.dentry));
 		path_put(&path);
+		/* ... and now kill it properly */
+		sock_release(sock);
 		return file;
 	}
 
@@ -1330,19 +1334,9 @@ SYSCALL_DEFINE3(socket, int, family, int, type, int, protocol)
 
 	retval = sock_create(family, type, protocol, &sock);
 	if (retval < 0)
-		goto out;
-
-	retval = sock_map_fd(sock, flags & (O_CLOEXEC | O_NONBLOCK));
-	if (retval < 0)
-		goto out_release;
-
-out:
-	/* It may be already another descriptor 8) Not kernel problem. */
-	return retval;
+		return retval;
 
-out_release:
-	sock_release(sock);
-	return retval;
+	return sock_map_fd(sock, flags & (O_CLOEXEC | O_NONBLOCK));
 }
 
 /*
@@ -1412,7 +1406,6 @@ SYSCALL_DEFINE4(socketpair, int, family, int, type, int, protocol,
 	newfile1 = sock_alloc_file(sock1, flags, NULL);
 	if (IS_ERR(newfile1)) {
 		err = PTR_ERR(newfile1);
-		sock_release(sock1);
 		sock_release(sock2);
 		goto out;
 	}
@@ -1420,7 +1413,6 @@ SYSCALL_DEFINE4(socketpair, int, family, int, type, int, protocol,
 	newfile2 = sock_alloc_file(sock2, flags, NULL);
 	if (IS_ERR(newfile2)) {
 		err = PTR_ERR(newfile2);
-		sock_release(sock2);
 		fput(newfile1);
 		goto out;
 	}
@@ -1549,7 +1541,6 @@ SYSCALL_DEFINE4(accept4, int, fd, struct sockaddr __user *, upeer_sockaddr,
 	if (IS_ERR(newfile)) {
 		err = PTR_ERR(newfile);
 		put_unused_fd(newfd);
-		sock_release(newsock);
 		goto out_put;
 	}
 
Signature · 1 line
2.11.0
Reviewed-by on v1 3/3
#7 lore raw

Re: [PATCH 3/3] make sock_alloc_file() do sock_release() on failures

Quoted 8 lines · Al Viro

This changes calling conventions (and simplifies the hell out the callers).  New rules: once struct socket had been passed to sock_alloc_file(), it's been consumed either by struct file or by sock_release() done by sock_alloc_file().  Either way the caller should not do sock_release() after that point.

---

Nice cleanup !

maintainer Acked-by on v1 1/1
#8 lore raw
In reply to Al Viro

From: Al Viro <[email protected]>
Date: Fri, 1 Dec 2017 00:20:27 +0000

Quoted 6 lines

1) massage sys_socketpair() (should be a pure cleanup)
2) fix and clean up kcm_clone() (-stable fodder)
3) switch sock_alloc_file() to new calling conventions.

It got some local testing, but it certainly needs more review.
Diffstat for the entire thing is

Series looks great to me:

author
#9 lore raw
Quoted 7 lines · David Miller

From: Al Viro <[email protected]>
Date: Fri, 1 Dec 2017 00:20:27 +0000

Quoted 4 lines

1) massage sys_socketpair() (should be a pure cleanup)
2) fix and clean up kcm_clone() (-stable fodder)
3) switch sock_alloc_file() to new calling conventions.

Quoted 6 lines
Quoted 2 lines

It got some local testing, but it certainly needs more review.
Diffstat for the entire thing is

Series looks great to me:

How do you prefer it to be handled? KCM one should go into everything since 4.6 (with trivial modifications in 4.11 and 4.12 - both had massaged the place around the call of kcm_clone() a bit, but this fix overwrites the entire area and that can be dropped into earlier kernels without any problems). I've put that into vfs.git#net-fixes and have the other two in vfs.git#for-davem on top of that, with you merging the latter into net-next.git and the former - into net.git. Is that OK with you, or would you prefer some other way of handling that kind of stuff?

maintainer
#10 lore raw

From: Al Viro <[email protected]>
Date: Mon, 4 Dec 2017 16:41:01 +0000

Quoted 15 lines · David Miller
Quoted 7 lines

From: Al Viro <[email protected]>
Date: Fri, 1 Dec 2017 00:20:27 +0000

Quoted 4 lines

1) massage sys_socketpair() (should be a pure cleanup)
2) fix and clean up kcm_clone() (-stable fodder)
3) switch sock_alloc_file() to new calling conventions.

Quoted 6 lines
Quoted 2 lines

It got some local testing, but it certainly needs more review.
Diffstat for the entire thing is

Series looks great to me:

Quoted 9 lines

How do you prefer it to be handled? KCM one should go into everything since 4.6 (with trivial modifications in 4.11 and 4.12 - both had massaged the place around the call of kcm_clone() a bit, but this fix overwrites the entire area and that can be dropped into earlier kernels without any problems). I've put that into vfs.git#net-fixes and have the other two in vfs.git#for-davem on top of that, with you merging the latter into net-next.git and the former - into net.git. Is that OK with you, or would you prefer some other way of handling that kind of stuff?

Why don't you resubmit this to netdev as a non-RFC, I'll queue it up to 'net' and -stable as well.

Thanks Al.

author
#11 lore raw
Quoted 28 lines · David Miller

From: Al Viro <[email protected]>
Date: Mon, 4 Dec 2017 16:41:01 +0000

Quoted 15 lines · David Miller
Quoted 7 lines

From: Al Viro <[email protected]>
Date: Fri, 1 Dec 2017 00:20:27 +0000

Quoted 4 lines

1) massage sys_socketpair() (should be a pure cleanup)
2) fix and clean up kcm_clone() (-stable fodder)
3) switch sock_alloc_file() to new calling conventions.

Quoted 6 lines
Quoted 2 lines

It got some local testing, but it certainly needs more review.
Diffstat for the entire thing is

Series looks great to me:

Quoted 9 lines

How do you prefer it to be handled? KCM one should go into everything since 4.6 (with trivial modifications in 4.11 and 4.12 - both had massaged the place around the call of kcm_clone() a bit, but this fix overwrites the entire area and that can be dropped into earlier kernels without any problems). I've put that into vfs.git#net-fixes and have the other two in vfs.git#for-davem on top of that, with you merging the latter into net-next.git and the former - into net.git. Is that OK with you, or would you prefer some other way of handling that kind of stuff?

Quoted 2 lines

Why don't you resubmit this to netdev as a non-RFC, I'll queue it up to 'net' and -stable as well.

Sent...