1. 24 6月, 2013 6 次提交
  2. 05 5月, 2013 2 次提交
    • J
      [CIFS] cifs: Rename cERROR and cFYI to cifs_dbg · f96637be
      Joe Perches 提交于
      It's not obvious from reading the macro names that these macros
      are for debugging.  Convert the names to a single more typical
      kernel style cifs_dbg macro.
      
      	cERROR(1, ...)   -> cifs_dbg(VFS, ...)
      	cFYI(1, ...)     -> cifs_dbg(FYI, ...)
      	cFYI(DBG2, ...)  -> cifs_dbg(NOISY, ...)
      
      Move the terminating format newline from the macro to the call site.
      
      Add CONFIG_CIFS_DEBUG function cifs_vfs_err to emit the
      "CIFS VFS: " prefix for VFS messages.
      
      Size is reduced ~ 1% when CONFIG_CIFS_DEBUG is set (default y)
      
      $ size fs/cifs/cifs.ko*
         text    data     bss     dec     hex filename
       265245	   2525	    132	 267902	  4167e	fs/cifs/cifs.ko.new
       268359    2525     132  271016   422a8 fs/cifs/cifs.ko.old
      
      Other miscellaneous changes around these conversions:
      
      o Miscellaneous typo fixes
      o Add terminating \n's to almost all formats and remove them
        from the macros to be more kernel style like.  A few formats
        previously had defective \n's
      o Remove unnecessary OOM messages as kmalloc() calls dump_stack
      o Coalesce formats to make grep easier,
        added missing spaces when coalescing formats
      o Use %s, __func__ instead of embedded function name
      o Removed unnecessary "cifs: " prefixes
      o Convert kzalloc with multiply to kcalloc
      o Remove unused cifswarn macro
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NJeff Layton <jlayton@redhat.com>
      Signed-off-by: NSteve French <smfrench@gmail.com>
      f96637be
    • D
      d455b72b
  3. 10 12月, 2012 1 次提交
  4. 06 12月, 2012 1 次提交
    • S
      SMB3 mounts fail with access denied to some servers · 52c0f4ad
      Steve French 提交于
      We were checking incorrectly if signatures were required to be sent,
      so were always sending signatures after the initial session establishment.
      For SMB3 mounts (vers=3.0) this was a problem because we were putting
      SMB2 signatures in SMB3 requests which would cause access denied
      on mount (the tree connection would fail).
      
      This might also be worth considering for stable (for 3.7), as the
      error message on mount (access denied) is confusing to users and
      there is no workaround if the server is configured to only
      support smb3.0. I am ok either way.
      
      CC: stable <stable@kernel.org>
      Signed-off-by: NSteve French <smfrench@gmail.com>
      Reviewed-by: NJeff Layton <jlayton@redhat.com>
      52c0f4ad
  5. 02 10月, 2012 1 次提交
  6. 27 9月, 2012 1 次提交
  7. 25 9月, 2012 24 次提交
  8. 25 7月, 2012 4 次提交