1 version 1.0.2 January 29, 2004
3 A Partial List of Known Problems and Missing Features
4 =====================================================
6 Contributions are welcome. There are plenty of opportunities
7 for visible, important contributions to this module. Here
8 is a partial list of the known problems and missing features:
10 a) Support for SecurityDescriptors for chmod/chgrp/chown so
11 these can be supported for Windows servers
13 b) Better pam/winbind integration
15 c) multi-user mounts - multiplexed sessionsetups over single vc
16 (ie tcp session) - prettying up needed
18 d) Kerberos/SPNEGO session setup support - (started)
20 e) NTLMv2 authentication (mostly implemented)
22 f) MD5-HMAC signing SMB PDUs when SPNEGO style SessionSetup
23 used (Kerberos or NTLMSSP). Signing alreadyimplemented for NTLM
24 and raw NTLMSSP already. This is important when enabling
25 extended security and mounting to Windows 2003 Servers
27 f) Directory entry caching relies on a 1 second timer, rather than
28 using FindNotify or equivalent. - (started)
30 g) A few byte range testcases fail due to POSIX vs. Windows/CIFS
31 style byte range lock differences
35 i) support for the Linux 2.5 kernel new feature get_xattr and set_xattr
36 which will allow us to expose dos attributes as well as real
39 k) finish writepages support (multi-page write behind for improved
40 performance) and syncpage
42 l) hook lower into the sockets api (as NFS/SunRPC does) to avoid the
43 extra copy in/out of the socket buffers in some cases.
45 m) finish support for IPv6
47 o) Better optimize open (and pathbased setfilesize) to reduce the
48 oplock breaks coming from windows srv. Piggyback identical file
49 opens on top of each other by incrementing reference count rather
50 than resending (helps reduce server resource utilization and avoid
51 spurious oplock breaks).
53 p) Improve performance of readpages by sending more than one read
54 at a time when 8 pages or more are requested.
57 KNOWN BUGS (updated January 30, 2004)
58 ====================================
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 but Samba has a bug currently handling
62 symlink text beginning with slash
63 2) follow_link and readdir code does not follow dfs junctions
65 3) create of new files to FAT partitions on Windows servers can
66 succeed but still return access denied (appears to be Windows
67 not client problem). NTFS partitions do not have this problem.
68 4) debug connectathon special test case nfs_idem (which does
69 some invalid symlink naming, or at least what Samba thinks
70 is an invalid symlink target).
71 5) debug connectation lock test case 10 which fails against
72 Samba (may be unmappable due to POSIX to Windows lock model
73 differences but worth investigating). Also debug Samba to
74 see why lock test case 7 takes longer to complete to Samba
79 1) check out max path names and max path name components against various server
82 2) Modify file portion of ltp so it can run against a mounted network
83 share and run it against cifs vfs.
85 3) Additional performance testing and optimization using iozone and similar -
86 there are some easy changes that can be done to parallelize sequential writes,
87 and when signing is disabled to request larger read sizes (larger than
88 negotiated size) and send larger write sizes to modern servers.
90 4) More exhaustively test the recently added NT4 support