Don't user forward declarations of internal kernel structures in headers
exported to userspace.
Move "struct completion;".
Move "struct task_struct;".
Link: http://lkml.kernel.org/r/20160713215808.GA22486@p183.telecom.by
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
struct file;
struct inode;
struct dentry;
struct file;
struct inode;
struct dentry;
struct user_namespace;
extern const kernel_cap_t __cap_empty_set;
struct user_namespace;
extern const kernel_cap_t __cap_empty_set;
#include <uapi/linux/sysctl.h>
/* For the /proc/sys support */
#include <uapi/linux/sysctl.h>
/* For the /proc/sys support */
struct ctl_table;
struct nsproxy;
struct ctl_table_root;
struct ctl_table;
struct nsproxy;
struct ctl_table_root;
/* User-level do most of the mapping between kernel and user
capabilities based on the version tag given by the kernel. The
kernel might be somewhat backwards compatible, but don't bet on
/* User-level do most of the mapping between kernel and user
capabilities based on the version tag given by the kernel. The
kernel might be somewhat backwards compatible, but don't bet on
#include <linux/types.h>
#include <linux/compiler.h>
#include <linux/types.h>
#include <linux/compiler.h>
#define CTL_MAXNAME 10 /* how many path components do we allow in a
call to sysctl? In other words, what is
the largest acceptable value for the nlen
#define CTL_MAXNAME 10 /* how many path components do we allow in a
call to sysctl? In other words, what is
the largest acceptable value for the nlen