(only 5 months later...)
Sure, how about this?
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@example.com>
### Diffstat output
./fs/nfs/file.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff .prev/fs/nfs/file.c ./fs/nfs/file.c
--- .prev/fs/nfs/file.c 2007-01-29 16:04:09.000000000 +1100
+++ ./fs/nfs/file.c 2007-01-29 16:04:45.000000000 +1100
@@ -434,8 +434,9 @@ static int do_vfs_lock(struct file *file
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"
+ " - error %d!\n",
+ __FUNCTION__, res);