Commit 46bae1a9 authored by Neil Brown's avatar Neil Brown Committed by Linus Torvalds

[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: default avatarNeil Brown <neilb@suse.de>
Acked-by: default avatarTrond Myklebust <trond.myklebust@fys.uio.no>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent ec268be3
...@@ -434,8 +434,9 @@ static int do_vfs_lock(struct file *file, struct file_lock *fl) ...@@ -434,8 +434,9 @@ static int do_vfs_lock(struct file *file, struct file_lock *fl)
BUG(); BUG();
} }
if (res < 0) if (res < 0)
printk(KERN_WARNING "%s: VFS is out of sync with lock manager!\n", dprintk(KERN_WARNING "%s: VFS is out of sync with lock manager"
__FUNCTION__); " - error %d!\n",
__FUNCTION__, res);
return res; return res;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment