On Mon, Aug 13, 2018 at 9:39 AM David Disseldorp <ddiss@xxxxxxx> wrote: > My preference would be to keep the original pseudo-xattr names until the > cifs.ko kernel module is (if ever) renamed. There are bound to be many > many other places where "cifs" is used, and renaming bit-by-bit doesn't > make much sense IMO. I think there are fewer than you might think - the remaining confusing 'cifs' names are mostly the two user space tools (cifsacl for example), and i am less concerned about that (distros can always fix that via a symlink if they keep getting pressure to disable everything relating to insecure 'cifs'). For the kernel, not sure if we have any remaining cases where you have to use 'cifs' (the name) since modprobe and mount work as expected (using 'smb3' prevents using vers=1.0, but is otherwise the same) There is precedent here in kernel code with aliases. -- Thanks, Steve
