linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@canonical.com>
To: Miklos Szeredi <miklos@szeredi.hu>, Andy Whitcroft <apw@canonical.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	mszeredi@suse.cz, Sedat Dilek <sedat.dilek@gmail.com>
Subject: [PATCH 3/5] overlayfs: follow header cleanup
Date: Tue,  1 May 2012 16:17:53 +0100	[thread overview]
Message-ID: <1335885475-11990-4-git-send-email-apw@canonical.com> (raw)
In-Reply-To: <1335885475-11990-1-git-send-email-apw@canonical.com>

The headers cleanup has removed a number of unnecessary includes from
various headers.  Fix up the now missing headers in overlayfs.

Signed-off-by: Andy Whitcroft <apw@canonical.com>
---
 fs/overlayfs/copy_up.c |    1 +
 fs/overlayfs/dir.c     |    1 +
 fs/overlayfs/readdir.c |    1 +
 fs/overlayfs/super.c   |    2 ++
 4 files changed, 5 insertions(+)

diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
index 398fa1c..87dbeee 100644
--- a/fs/overlayfs/copy_up.c
+++ b/fs/overlayfs/copy_up.c
@@ -14,6 +14,7 @@
 #include <linux/xattr.h>
 #include <linux/security.h>
 #include <linux/uaccess.h>
+#include <linux/sched.h>
 #include "overlayfs.h"
 
 #define OVL_COPY_UP_CHUNK_SIZE (1 << 20)
diff --git a/fs/overlayfs/dir.c b/fs/overlayfs/dir.c
index 57bbb94..00aa6d9 100644
--- a/fs/overlayfs/dir.c
+++ b/fs/overlayfs/dir.c
@@ -11,6 +11,7 @@
 #include <linux/namei.h>
 #include <linux/xattr.h>
 #include <linux/security.h>
+#include <linux/cred.h>
 #include "overlayfs.h"
 
 static const char *ovl_whiteout_symlink = "(overlay-whiteout)";
diff --git a/fs/overlayfs/readdir.c b/fs/overlayfs/readdir.c
index ed8fbad..0797efb 100644
--- a/fs/overlayfs/readdir.c
+++ b/fs/overlayfs/readdir.c
@@ -14,6 +14,7 @@
 #include <linux/xattr.h>
 #include <linux/rbtree.h>
 #include <linux/security.h>
+#include <linux/cred.h>
 #include "overlayfs.h"
 
 struct ovl_cache_entry {
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index 10cafe0..b679019 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -16,6 +16,8 @@
 #include <linux/parser.h>
 #include <linux/module.h>
 #include <linux/seq_file.h>
+#include <linux/cred.h>
+#include <linux/sched.h>
 #include "overlayfs.h"
 
 MODULE_AUTHOR("Miklos Szeredi <miklos@szeredi.hu>");
-- 
1.7.9.5

  parent reply	other threads:[~2012-05-01 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 15:17 [PATCH 0/5] overlayfs v3.4-rc5 updates Andy Whitcroft
2012-05-01 15:17 ` [PATCH 1/5] inode_only_permission: export inode level permissions checks Andy Whitcroft
2012-05-01 15:17 ` [PATCH 2/5] overlayfs: switch to use inode_only_permissions Andy Whitcroft
2012-05-01 15:17 ` Andy Whitcroft [this message]
2012-05-01 15:17 ` [PATCH 4/5] overlayfs: switch from d_alloc_root() to d_make_root() Andy Whitcroft
2012-05-01 15:17 ` [PATCH 5/5] overlayfs: update touch_atime() usage Andy Whitcroft
2012-05-14 11:20 ` [PATCH 0/5] overlayfs v3.4-rc5 updates Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1335885475-11990-4-git-send-email-apw@canonical.com \
    --to=apw@canonical.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@suse.cz \
    --cc=sedat.dilek@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).