From: Paul Mundt <lethal@linux-sh.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-next@vger.kernel.org
Subject: [PATCH -next] fanotify: select ANON_INODES.
Date: Tue, 24 Nov 2009 15:02:56 +0900 [thread overview]
Message-ID: <20091124060256.GA30779@linux-sh.org> (raw)
fanotify references anon_inode_getfd(), which is only available with
ANON_INODES enabled. Presently this bails out with the following:
LD vmlinux
fs/built-in.o: In function `sys_fanotify_init':
(.text+0x26d1c): undefined reference to `anon_inode_getfd'
make: *** [vmlinux] Error 1
which is trivially corrected by adding an ANON_INODES select.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
---
fs/notify/fanotify/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/notify/fanotify/Kconfig b/fs/notify/fanotify/Kconfig
index f9d7ae0..668e5df 100644
--- a/fs/notify/fanotify/Kconfig
+++ b/fs/notify/fanotify/Kconfig
@@ -1,6 +1,7 @@
config FANOTIFY
bool "Filesystem wide access notification"
select FSNOTIFY
+ select ANON_INODES
default y
---help---
Say Y here to enable fanotify suport. fanotify is a file access
next reply other threads:[~2009-11-24 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 6:02 Paul Mundt [this message]
2009-11-24 13:25 ` [PATCH -next] fanotify: select ANON_INODES Eric Paris
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=20091124060256.GA30779@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=eparis@redhat.com \
--cc=linux-next@vger.kernel.org \
/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).