net: Remove the err argument from sock_from_file
Currently, the sock_from_file prototype takes an "err" pointer that is either not set or set to -ENOTSOCK IFF the returned socket is NULL. This makes the error redundant and it is ignored by a few callers. This patch simplifies the API by letting callers deduce the error based on whether the returned socket is NULL or not. Suggested-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Florent Revest <revest@google.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Reviewed-by: KP Singh <kpsingh@google.com> Link: https://lore.kernel.org/bpf/20201204113609.1850150-1-revest@google.com
This commit is contained in:
committed by
Daniel Borkmann
parent
5c667dca71
commit
dba4a9256b
@@ -240,7 +240,7 @@ int sock_sendmsg(struct socket *sock, struct msghdr *msg);
|
||||
int sock_recvmsg(struct socket *sock, struct msghdr *msg, int flags);
|
||||
struct file *sock_alloc_file(struct socket *sock, int flags, const char *dname);
|
||||
struct socket *sockfd_lookup(int fd, int *err);
|
||||
struct socket *sock_from_file(struct file *file, int *err);
|
||||
struct socket *sock_from_file(struct file *file);
|
||||
#define sockfd_put(sock) fput(sock->file)
|
||||
int net_ratelimit(void);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user