TODO 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. Version 2.11 September 13, 2017
  2. A Partial List of Missing Features
  3. ==================================
  4. Contributions are welcome. There are plenty of opportunities
  5. for visible, important contributions to this module. Here
  6. is a partial list of the known problems and missing features:
  7. a) SMB3 (and SMB3.02) missing optional features:
  8. - multichannel (started), integration with RDMA
  9. - directory leases (improved metadata caching), started (root dir only)
  10. - T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl
  11. currently the only two server side copy mechanisms supported)
  12. b) improved sparse file support
  13. c) Directory entry caching relies on a 1 second timer, rather than
  14. using Directory Leases, currently only the root file handle is cached longer
  15. d) quota support (needs minor kernel change since quota calls
  16. to make it to network filesystems or deviceless filesystems)
  17. e) Compounding (in progress) to reduce number of roundtrips, and also
  18. better optimize open to reduce redundant opens (using reference counts more).
  19. f) Finish inotify support so kde and gnome file list windows
  20. will autorefresh (partially complete by Asser). Needs minor kernel
  21. vfs change to support removing D_NOTIFY on a file.
  22. g) Add GUI tool to configure /proc/fs/cifs settings and for display of
  23. the CIFS statistics (started)
  24. h) implement support for security and trusted categories of xattrs
  25. (requires minor protocol extension) to enable better support for SELINUX
  26. i) Add support for tree connect contexts (see MS-SMB2) a new SMB3.1.1 protocol
  27. feature (may be especially useful for virtualization).
  28. j) Create UID mapping facility so server UIDs can be mapped on a per
  29. mount or a per server basis to client UIDs or nobody if no mapping
  30. exists. Also better integration with winbind for resolving SID owners
  31. k) Add tools to take advantage of more smb3 specific ioctls and features
  32. (passthrough ioctl/fsctl for sending various SMB3 fsctls to the server
  33. is in progress)
  34. l) encrypted file support
  35. m) improved stats gathering, tools (perhaps integration with nfsometer?)
  36. n) allow setting more NTFS/SMB3 file attributes remotely (currently limited to compressed
  37. file attribute via chflags) and improve user space tools for managing and
  38. viewing them.
  39. o) mount helper GUI (to simplify the various configuration options on mount)
  40. p) Add support for witness protocol (perhaps ioctl to cifs.ko from user space
  41. tool listening on witness protocol RPC) to allow for notification of share
  42. move, server failover, and server adapter changes. And also improve other
  43. failover scenarios, e.g. when client knows multiple DFS entries point to
  44. different servers, and the server we are connected to has gone down.
  45. q) Allow mount.cifs to be more verbose in reporting errors with dialect
  46. or unsupported feature errors.
  47. r) updating cifs documentation, and user guide.
  48. s) Addressing bugs found by running a broader set of xfstests in standard
  49. file system xfstest suite.
  50. t) split cifs and smb3 support into separate modules so legacy (and less
  51. secure) CIFS dialect can be disabled in environments that don't need it
  52. and simplify the code.
  53. v) POSIX Extensions for SMB3.1.1 (started, create and mkdir support added
  54. so far).
  55. KNOWN BUGS
  56. ====================================
  57. See http://bugzilla.samba.org - search on product "CifsVFS" for
  58. current bug list. Also check http://bugzilla.kernel.org (Product = File System, Component = CIFS)
  59. 1) existing symbolic links (Windows reparse points) are recognized but
  60. can not be created remotely. They are implemented for Samba and those that
  61. support the CIFS Unix extensions, although earlier versions of Samba
  62. overly restrict the pathnames.
  63. 2) follow_link and readdir code does not follow dfs junctions
  64. but recognizes them
  65. Misc testing to do
  66. ==================
  67. 1) check out max path names and max path name components against various server
  68. types. Try nested symlinks (8 deep). Return max path name in stat -f information
  69. 2) Improve xfstest's cifs/smb3 enablement and adapt xfstests where needed to test
  70. cifs/smb3 better
  71. 3) Additional performance testing and optimization using iozone and similar -
  72. there are some easy changes that can be done to parallelize sequential writes,
  73. and when signing is disabled to request larger read sizes (larger than
  74. negotiated size) and send larger write sizes to modern servers.
  75. 4) More exhaustively test against less common servers