Commit:     46bae1a9a767f3ae8e636d96f9b95703df34b398
Parent:     ec268be36e79d99443efc4be3a617d6efc6f719b
Author:     Neil Brown <[EMAIL PROTECTED]>
AuthorDate: Tue Jan 30 14:36:01 2007 -0800
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Tue Jan 30 16:01:35 2007 -0800

    [PATCH] Remove warning: VFS is out of sync with lock manager
    But keep it as a dprintk
    The message can be generated in a quite normal situation:
     If a 'lock' request is interrupted, then the lock client needs to
      record that the server has the lock, incase it does.
     When we come the unlock, the server might say it doesn't, even
      though we think it does (or might) and this generates the message.
    Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
    Acked-by: Trond Myklebust <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 fs/nfs/file.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/fs/nfs/file.c b/fs/nfs/file.c
index fab20d0..9e4a2b7 100644
--- a/fs/nfs/file.c
+++ b/fs/nfs/file.c
@@ -434,8 +434,9 @@ static int do_vfs_lock(struct file *file, struct file_lock 
        if (res < 0)
-               printk(KERN_WARNING "%s: VFS is out of sync with lock 
-                               __FUNCTION__);
+               dprintk(KERN_WARNING "%s: VFS is out of sync with lock manager"
+                       " - error %d!\n",
+                               __FUNCTION__, res);
        return res;
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to