NFS: dprintk() should not print negative fileids and inode numbers
authorNiels de Vos <ndevos@redhat.com>
Tue, 17 Dec 2013 17:20:16 +0000 (18:20 +0100)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Sun, 5 Jan 2014 20:51:23 +0000 (15:51 -0500)
commit1e8968c5b0582392d5f132422f581e3ebc24e627
tree1fbb842ca0b18d421f1e74b046324e38dbcb58c3
parenta8c2275493b866961f4429a741251c630c4fc6d7
NFS: dprintk() should not print negative fileids and inode numbers

A fileid in NFS is a uint64. There are some occurrences where dprintk()
outputs a signed fileid. This leads to confusion and more difficult to
read debugging (negative fileids matching positive inode numbers).

Signed-off-by: Niels de Vos <ndevos@redhat.com>
CC: Santosh Pradhan <spradhan@redhat.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/dir.c
fs/nfs/direct.c
fs/nfs/file.c
fs/nfs/inode.c
fs/nfs/nfs3acl.c
fs/nfs/nfs4filelayout.c
fs/nfs/read.c
fs/nfs/write.c