1. 10 Nov, 2016 1 commit
  2. 07 Nov, 2016 4 commits
  3. 24 Oct, 2016 2 commits
    • Arnd Bergmann's avatar
      NFSv4.1: work around -Wmaybe-uninitialized warning · 68a56400
      Arnd Bergmann authored
      A bugfix introduced a harmless gcc warning in nfs4_slot_seqid_in_use
      if we enable -Wmaybe-uninitialized again:
      
      fs/nfs/nfs4session.c:203:54: error: 'cur_seq' may be used uninitialized in this function [-Werror=maybe-uninitialized]
      
      gcc is not smart enough to conclude that the IS_ERR/PTR_ERR pair
      results in a nonzero return value here. Using PTR_ERR_OR_ZERO()
      instead makes this clear to the compiler.
      
      The warning originally did not appear in v4.8 as it was globally
      disabled, but the bugfix that introduced the warning got backported
      to stable kernels which again enable it, and this is now the only
      warning in the v4.7 builds.
      
      Fixes: e09c978a ("NFSv4.1: Fix Oopsable condition in server callback races")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Trond Myklebust <trond.myklebust@primarydata.com>
      Signed-off-by: default avatarAnna Schumaker <Anna.Schumaker@Netapp.com>
      68a56400
    • Benjamin Coddington's avatar
      NFS: Trim extra slash in v4 nfs_path · 86a6c211
      Benjamin Coddington authored
      A NFSv4 mount of a subdirectory will show an extra slash (as in
      'server://path') in proc's mountinfo which will not match the device name
      and path.  This can cause problems for programs searching for the mount.
      Fix this by checking for a leading slash in the dentry path, if so trim
      away any trailing slashes in the device name.
      Signed-off-by: default avatarBenjamin Coddington <bcodding@redhat.com>
      Signed-off-by: default avatarAnna Schumaker <Anna.Schumaker@Netapp.com>
      86a6c211
  4. 19 Oct, 2016 1 commit
  5. 13 Oct, 2016 1 commit
  6. 04 Oct, 2016 2 commits
  7. 30 Sep, 2016 5 commits
  8. 29 Sep, 2016 1 commit
  9. 27 Sep, 2016 23 commits