CacheFiles: Don't log lookup/create failing with ENOBUFS
authorDavid Howells <dhowells@redhat.com>
Thu, 19 Nov 2009 18:12:08 +0000 (18:12 +0000)
committerDavid Howells <dhowells@redhat.com>
Thu, 19 Nov 2009 18:12:08 +0000 (18:12 +0000)
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>
fs/cachefiles/interface.c

index 9d3c426044aebb2f329929e4e1a2c71f71bd32e4..27089311fbea467b4ca6ec7d6522ae0525231c6f 100644 (file)
@@ -147,8 +147,9 @@ static int cachefiles_lookup_object(struct fscache_object *_object)
                cachefiles_attr_changed(&object->fscache);
 
        if (ret < 0 && ret != -ETIMEDOUT) {
-               printk(KERN_WARNING "CacheFiles: Lookup failed error %d\n",
-                      ret);
+               if (ret != -ENOBUFS)
+                       printk(KERN_WARNING
+                              "CacheFiles: Lookup failed error %d\n", ret);
                fscache_object_lookup_error(&object->fscache);
        }