linux-kernel - [PATCH 1/1] NFS: Fix build breakge when CONFIG_NFS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1356091050-17201-1-git-send-email-vaibhav.bedia@ti.com>
Date:	Fri, 21 Dec 2012 17:27:30 +0530
From:	Vaibhav Bedia <vaibhav.bedia@...com>
To:	<linux-kernel@...r.kernel.org>, <linux-nfs@...r.kernel.org>,
	<Trond.Myklebust@...app.com>
CC:	Vaibhav Bedia <vaibhav.bedia@...com>
Subject: [PATCH 1/1] NFS: Fix build breakge when CONFIG_NFS_FSCACHE is not defined

Commit de242c0b (NFS: Use FS-Cache invalidation) introduced
a build breakge for the case where CONFIG_NFS_FSCACHE is not
defined.

...
fs/nfs/inode.c: In function 'nfs_invalidate_mapping':
fs/nfs/inode.c: error: implicit declaration of function 'nfs_fscache_wait_on_invalidate'
make[2]: *** [fs/nfs/inode.o] Error 1

Add an empty function similar to fix this.

Signed-off-by: Vaibhav Bedia <vaibhav.bedia@...com>
---
 fs/nfs/fscache.h |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/fs/nfs/fscache.h b/fs/nfs/fscache.h
index 277b027..e06d4f4 100644
--- a/fs/nfs/fscache.h
+++ b/fs/nfs/fscache.h
@@ -223,6 +223,8 @@ static inline void nfs_readpage_to_fscache(struct inode *inode,
 
 static inline void nfs_fscache_invalidate(struct inode *inode) {}
 
+static inline void nfs_fscache_wait_on_invalidate(struct inode *inode) {}
+
 static inline const char *nfs_server_fscache_state(struct nfs_server *server)
 {
 	return "no ";
-- 
1.7.0.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/