[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKYAXd_p1MrB2G25_p52OfppfSUcEWQEVxgJbBikAe3GZrJFhw@mail.gmail.com>
Date: Thu, 1 Apr 2021 22:36:31 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: Ralph Boehme <slow@...ba.org>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
COMMON INTERNET FILE SYSTEM SERVER
<linux-cifs@...r.kernel.org>,
COMMON INTERNET FILE SYSTEM SERVER
<linux-cifsd-devel@...ts.sourceforge.net>,
kernel-janitors@...r.kernel.org,
open list <linux-kernel@...r.kernel.org>,
Steve French <sfrench@...ba.org>, colin.king@...onical.com,
Muhammad Usama Anjum <musamaanjum@...il.com>
Subject: Re: [Linux-cifsd-devel] [PATCH] cifsd: use kfree to free memory
allocated by kzalloc
2021-04-01 22:14 GMT+09:00, Ralph Boehme <slow@...ba.org>:
> Am 4/1/21 um 2:59 PM schrieb Namjae Jeon:
>> 2021-04-01 21:50 GMT+09:00, Ralph Boehme <slow@...ba.org>:
>>> fwiw, while at it what about renaming everything that still references
>>> "cifs" to "smb" ? This is not the 90's... :)
>> It is also used with the name "ksmbd". So function and variable prefix
>> are used with ksmbd.
>
> well, I was thinking of this:
>
> > +++ b/fs/cifsd/...
>
> We should really stop using the name cifs for modern implementation of
> SMB{23} and the code should not be added as fs/cifsd/ to the kernel.
As I know, currently "cifs" is being used for the subdirectory name
for historical reasons and to avoid confusions, even though the CIFS
(SMB1) dialect is no longer recommended.
>
> Cheers!
> -slow
>
> --
> Ralph Boehme, Samba Team https://samba.org/
> Samba Developer, SerNet GmbH https://sernet.de/en/samba/
> GPG-Fingerprint FAE2C6088A24252051C559E4AA1E9B7126399E46
>
>
Powered by blists - more mailing lists