From: Namjae Jeon <linkinjeon@kernel.org>
To: Ralph Boehme <slow@samba.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
COMMON INTERNET FILE SYSTEM SERVER <linux-cifs@vger.kernel.org>,
COMMON INTERNET FILE SYSTEM SERVER
<linux-cifsd-devel@lists.sourceforge.net>,
kernel-janitors@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Steve French <sfrench@samba.org>,
colin.king@canonical.com,
Muhammad Usama Anjum <musamaanjum@gmail.com>
Subject: Re: [Linux-cifsd-devel] [PATCH] cifsd: use kfree to free memory allocated by kzalloc
Date: Thu, 1 Apr 2021 22:36:31 +0900 [thread overview]
Message-ID: <CAKYAXd_p1MrB2G25_p52OfppfSUcEWQEVxgJbBikAe3GZrJFhw@mail.gmail.com> (raw)
In-Reply-To: <2b758812-f00b-9465-c24e-763912748809@samba.org>
2021-04-01 22:14 GMT+09:00, Ralph Boehme <slow@samba.org>:
> Am 4/1/21 um 2:59 PM schrieb Namjae Jeon:
>> 2021-04-01 21:50 GMT+09:00, Ralph Boehme <slow@samba.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
>
>
next prev parent reply other threads:[~2021-04-01 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 11:39 [PATCH] cifsd: use kfree to free memory allocated by kzalloc Muhammad Usama Anjum
2021-04-01 11:50 ` Dan Carpenter
2021-04-01 12:43 ` [Linux-cifsd-devel] " Namjae Jeon
2021-04-01 12:50 ` Ralph Boehme
2021-04-01 12:59 ` Namjae Jeon
2021-04-01 13:14 ` Ralph Boehme
2021-04-01 13:36 ` Namjae Jeon [this message]
2021-04-01 21:04 ` Tom Talpey
2021-04-07 0:17 ` ronnie sahlberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKYAXd_p1MrB2G25_p52OfppfSUcEWQEVxgJbBikAe3GZrJFhw@mail.gmail.com \
--to=linkinjeon@kernel.org \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=musamaanjum@gmail.com \
--cc=sfrench@samba.org \
--cc=slow@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).