Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 17 4月, 2009 1 次提交
  3. 21 2月, 2009 2 次提交
  5. 21 11月, 2008 1 次提交
    • S
      [CIFS] Do not attempt to close invalidated file handles · ddb4cbfc
      由 Steve French 提交于 
      If a connection with open file handles has gone down
and come back up and reconnected without reopening
the file handle yet, do not attempt to send an SMB close
request for this handle in cifs_close.  We were
checking for the connection being invalid in cifs_close
but since the connection may have been reconnected
we also need to check whether the file handle
was marked invalid (otherwise we could close the
wrong file handle by accident).
Acked-by: NJeff Layton <jlayton@redhat.com>
Signed-off-by: NSteve French <sfrench@us.ibm.com>
      ddb4cbfc
  7. 21 10月, 2008 1 次提交
    • J
      [CIFS] fix saving of resume key before CIFSFindNext · a364bc0b
      由 Jeff Layton 提交于 
      We recently fixed the cifs readdir code so that it saves the resume key
before calling CIFSFindNext. Unfortunately, this assumes that we have
just done a CIFSFindFirst (or FindNext) and have resume info to save.
This isn't necessarily the case. Fix the code to save resume info if we
had to reinitiate the search, and after a FindNext.

This fixes connectathon basic test6 against NetApp filers.
Signed-off-by: NJeff Layton <jlayton@redhat.com>
CC: Stable <stable@kernel.org>
Signed-off-by: NSteve French <sfrench@us.ibm.com>
      a364bc0b
  9. 08 10月, 2008 1 次提交
    • S
      [CIFS] make sure we have the right resume info before calling CIFSFindNext · 0752f152
      由 Steve French 提交于 
      When we do a seekdir() or equivalent, we usually end up doing a
FindFirst call and then call FindNext until we get to the offset that we
want. The problem is that when we call FindNext, the code usually
doesn't have the proper info (mostly, the filename of the entry from the
last search) to resume the search.

Add a "last_entry" field to the cifs_search_info that points to the last
entry in the search. We calculate this pointer by using the
LastNameOffset field from the search parms that are returned. We then
use that info to do a cifs_save_resume_key before we call CIFSFindNext.

This patch allows CIFS to reliably pass the "telldir" connectathon test.
Signed-off-by: NJeff Layton <jlayton@redhat.com>
CC: Stable <stable@kernel.org>
Signed-off-by: NSteve French <sfrench@us.ibm.com>
      0752f152
  11. 24 7月, 2008 1 次提交
  13. 24 5月, 2008 2 次提交
  15. 14 5月, 2008 1 次提交
    • S
      [CIFS] don't explicitly do a FindClose on rewind when directory search has ended · 77c57ec8
      由 Steve French 提交于 
      Do the following series of operations on a CIFS share:

    opendir(dir)
    readdir(dir)
    unlink(file in dir)
    rewinddir(dir)
    readdir(dir)

If the readdir read all entries in the directory this will make CIFS throw an error like this:

     CIFS VFS: Send error in FindClose = -9

CIFS requests "Close at end of search" of the server by setting this bit when issuing FindFirst or FindNext.  Therefore when all search entries are returned, the server may return "end of search" and close the search implicitly when this bit is set by the client on the request.  We check for this when a readdir is explicitly closed - but when the client notices that a directory has changed after the last operation, we attempt to close the directory before reopening by reissuing a second FindFirst. But, the directory may already been implicitly closed (due to end of search) because the first readdir finished. So we only want to issue a FindClose call in this case when we don't expect it to already be closed.
Signed-off-by: NJeff Layton <jlayton@redhat.com>
Signed-off-by: NSteve French <sfrench@us.ibm.com>
      77c57ec8
  17. 29 4月, 2008 1 次提交
  19. 13 2月, 2008 1 次提交
  21. 08 2月, 2008 1 次提交
  23. 09 11月, 2007 1 次提交
    • S
      [CIFS] Fix stale mode after readdir when cifsacl specified · a6f8de3d
      由 Steve French 提交于 
      When mounted with cifsacl mount option, readdir can not
instantiate the inode with the estimated mode based on the ACL
for each file since we have not queried for the ACL for
each of these files yet.  So set the refresh time to zero
for these inodes so that the next stat will cause the client
to go to the server for the ACL info so we can build the estimated
mode (this means we also will issue an extra QueryPathInfo if
the stat happens within 1 second, but this is trivial compared to
the time required to open/getacl/close for each).

ls -l is slower when cifsacl mount option is specified, but
displays correct mode information.
Signed-off-by: NShirish Pargaonkar <shirishp@us.ibm.com>
Signed-off-by: NSteve French <sfrench@us.ibm.com>
      a6f8de3d
  25. 06 11月, 2007 1 次提交
  27. 13 10月, 2007 1 次提交
  29. 31 8月, 2007 1 次提交
  31. 19 7月, 2007 1 次提交
  33. 13 7月, 2007 1 次提交
  35. 08 7月, 2007 2 次提交
  37. 07 7月, 2007 1 次提交
  39. 09 5月, 2007 1 次提交
  41. 01 5月, 2007 1 次提交
    • S
      [CIFS] UID/GID override on CIFS mounts to Samba · 4523cc30
      由 Steve French 提交于 
      When CIFS Unix Extensions are negotiated we get the Unix uid and gid
owners of the file from the server (on the Unix Query Path Info
levels), but if the server's uids don't match the client uid's users
were having to disable the Unix Extensions (which turned off features
they still wanted).   The changeset patch allows users to override uid
and/or gid for file/directory owner with a default uid and/or gid
specified at mount (as is often done when mounting from Linux cifs
client to Windows server).  This changeset also displays the uid
and gid used by default in /proc/mounts (if applicable).

Also cleans up code by adding some of the missing spaces after
"if" keywords per-kernel style guidelines (as suggested by Randy Dunlap
when he reviewed the patch).
Signed-off-by: NSteve French <sfrench@us.ibm.com>
      4523cc30
  43. 25 4月, 2007 1 次提交
  45. 03 4月, 2007 1 次提交
  47. 10 3月, 2007 1 次提交
  49. 27 2月, 2007 1 次提交
  51. 17 2月, 2007 1 次提交
  53. 09 2月, 2007 1 次提交
  55. 07 2月, 2007 1 次提交
  57. 09 12月, 2006 1 次提交
  59. 31 10月, 2006 1 次提交
  61. 12 10月, 2006 2 次提交
  63. 07 10月, 2006 1 次提交
  65. 02 10月, 2006 1 次提交
  67. 28 9月, 2006 1 次提交
  69. 27 9月, 2006 1 次提交
  71. 07 9月, 2006 1 次提交