[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yul5hBFmwoOQ0cxG@casper.infradead.org>
Date: Tue, 2 Aug 2022 20:22:44 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Enzo Matsumiya <ematsumiya@...e.de>
Cc: linux-cifs@...r.kernel.org, smfrench@...il.com, pc@....nz,
ronniesahlberg@...il.com, nspmangalore@...il.com,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
tom@...pey.com, samba-technical@...ts.samba.org,
pshilovsky@...ba.org, jlayton@...nel.org, rpenny@...ba.org
Subject: Re: [RFC PATCH v2 0/5] Rename "cifs" module to "smbfs"
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?
Powered by blists - more mailing lists