diff options
| author | Jeff Layton <jlayton@redhat.com> | 2011-08-08 11:50:24 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-08-29 13:29:06 -0700 |
| commit | b732c7ad1f6e6056dd898de7987665d4c490c78d (patch) | |
| tree | 063b60aebb505805e1383c3bbf4506ffd233f13d | |
| parent | 9a420aaeab0231727fc620fca9cd0e46e6438e93 (diff) | |
| download | kernel_samsung_aries-b732c7ad1f6e6056dd898de7987665d4c490c78d.zip kernel_samsung_aries-b732c7ad1f6e6056dd898de7987665d4c490c78d.tar.gz kernel_samsung_aries-b732c7ad1f6e6056dd898de7987665d4c490c78d.tar.bz2 | |
cifs: demote cERROR in build_path_from_dentry to cFYI
commit fa71f447065f676157ba6a2c121ba419818fc559 upstream.
Running the cthon tests on a recent kernel caused this message to pop
occasionally:
CIFS VFS: did not end path lookup where expected namelen is 0
Some added debugging showed that namelen and dfsplen were both 0 when
this occurred. That means that the read_seqretry returned true.
Assuming that the comment inside the if statement is true, this should
be harmless and just means that we raced with a rename. If that is the
case, then there's no need for alarm and we can demote this to cFYI.
While we're at it, print the dfsplen too so that we can see what
happened here if the message pops during debugging.
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| -rw-r--r-- | fs/cifs/dir.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/cifs/dir.c b/fs/cifs/dir.c index d8d26f3..16cdd6d 100644 --- a/fs/cifs/dir.c +++ b/fs/cifs/dir.c @@ -110,8 +110,8 @@ cifs_bp_rename_retry: } rcu_read_unlock(); if (namelen != dfsplen || read_seqretry(&rename_lock, seq)) { - cERROR(1, "did not end path lookup where expected namelen is %d", - namelen); + cFYI(1, "did not end path lookup where expected. namelen=%d " + "dfsplen=%d", namelen, dfsplen); /* presumably this is only possible if racing with a rename of one of the parent directories (we can not lock the dentries above us to prevent this, but retrying should be harmless) */ |