linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@canonical.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	vaurora@redhat.com, neilb@suse.de, viro@zeniv.linux.org.uk,
	Andy Whitcroft <apw@canonical.com>
Subject: [PATCH 1/2] overlayfs: export security_inode_permission to allow overlayfs to be modular
Date: Fri,  1 Oct 2010 18:48:01 +0100	[thread overview]
Message-ID: <1285955282-10240-2-git-send-email-apw@canonical.com> (raw)
In-Reply-To: <1285955282-10240-1-git-send-email-apw@canonical.com>

When compiling overlayfs as a module we end up with an unknown symbol
'security_inode_permission'.  Export it.

Signed-off-by: Andy Whitcroft <apw@canonical.com>
---
 security/security.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/security/security.c b/security/security.c
index ca39940..b8329cc 100644
--- a/security/security.c
+++ b/security/security.c
@@ -556,6 +556,7 @@ int security_inode_permission(struct inode *inode, int mask)
 		return 0;
 	return security_ops->inode_permission(inode, mask);
 }
+EXPORT_SYMBOL_GPL(security_inode_permission);
 
 int security_inode_setattr(struct dentry *dentry, struct iattr *attr)
 {
-- 
1.7.0.4

  reply	other threads:[~2010-10-01 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 17:48 [PATCH 0/2] overlayfs: module and statfs fixes Andy Whitcroft
2010-10-01 17:48 ` Andy Whitcroft [this message]
2010-10-01 17:48 ` [PATCH 2/2] overlayfs: add statfs support Andy Whitcroft
2010-10-04  9:49 ` [PATCH 0/2] overlayfs: module and statfs fixes 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=1285955282-10240-2-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=neilb@suse.de \
    --cc=vaurora@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).