aboutsummaryrefslogtreecommitdiffstats
path: root/fs/cachefiles/interface.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2009-11-19 13:12:08 -0500
committerDavid Howells <dhowells@redhat.com>2009-11-19 13:12:08 -0500
commit14e69647c868459bcb910f771851ca7c699efd21 (patch)
treeeaf14450c1dd6894ff7db727b6e8afe179cae6a0 /fs/cachefiles/interface.c
parentfee096deb4f33897937b974cb2c5168bab7935be (diff)
CacheFiles: Don't log lookup/create failing with ENOBUFS
Don't log the CacheFiles lookup/create object routined failing with ENOBUFS as under high memory load or high cache load they can do this quite a lot. This error simply means that the requested object cannot be created on disk due to lack of space, or due to failure of the backing filesystem to find sufficient resources. Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'fs/cachefiles/interface.c')
-rw-r--r--fs/cachefiles/interface.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/fs/cachefiles/interface.c b/fs/cachefiles/interface.c
index 9d3c426044ae..27089311fbea 100644
--- a/fs/cachefiles/interface.c
+++ b/fs/cachefiles/interface.c
@@ -147,8 +147,9 @@ static int cachefiles_lookup_object(struct fscache_object *_object)
147 cachefiles_attr_changed(&object->fscache); 147 cachefiles_attr_changed(&object->fscache);
148 148
149 if (ret < 0 && ret != -ETIMEDOUT) { 149 if (ret < 0 && ret != -ETIMEDOUT) {
150 printk(KERN_WARNING "CacheFiles: Lookup failed error %d\n", 150 if (ret != -ENOBUFS)
151 ret); 151 printk(KERN_WARNING
152 "CacheFiles: Lookup failed error %d\n", ret);
152 fscache_object_lookup_error(&object->fscache); 153 fscache_object_lookup_error(&object->fscache);
153 } 154 }
154 155