Message ID | 20220802190048.19881-1-ematsumiya@suse.de |
---|---|
Headers | show |
Series | Rename "cifs" module to "smbfs" | expand |
On Tue, Aug 02, 2022 at 04:00:43PM -0300, Enzo Matsumiya wrote: > Hi, > > As part of the ongoing effort to remove the "cifs" nomenclature from the > Linux SMB client, I'm proposing the rename of the module to "smbfs". > > As it's widely known, CIFS is associated to SMB1.0, which, in turn, is > associated with the security issues it presented in the past. Using > "SMBFS" makes clear what's the protocol in use for outsiders, but also > unties it from any particular protocol version. It also fits in the > already existing "fs/smbfs_common" and "fs/ksmbd" naming scheme. > > This short patch series only changes directory names and includes/ifdefs in > headers and source code, and updates docs to reflect the rename. Other > than that, no source code/functionality is modified (WIP though). Why did you not reply to Jeff Layton's concern before posting a v2?
On 08/02, Matthew Wilcox wrote: >On Tue, Aug 02, 2022 at 04:00:43PM -0300, Enzo Matsumiya wrote: >> Hi, >> >> As part of the ongoing effort to remove the "cifs" nomenclature from the >> Linux SMB client, I'm proposing the rename of the module to "smbfs". >> >> As it's widely known, CIFS is associated to SMB1.0, which, in turn, is >> associated with the security issues it presented in the past. Using >> "SMBFS" makes clear what's the protocol in use for outsiders, but also >> unties it from any particular protocol version. It also fits in the >> already existing "fs/smbfs_common" and "fs/ksmbd" naming scheme. >> >> This short patch series only changes directory names and includes/ifdefs in >> headers and source code, and updates docs to reflect the rename. Other >> than that, no source code/functionality is modified (WIP though). > >Why did you not reply to Jeff Layton's concern before posting a v2? Hm, I was pretty sure I did. Sorry about that, I got confused on how my mail client organized the replies to the initial thread. Replying to Jeff right now.