From: Tom Talpey <tom@talpey.com>
To: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
samba-technical <samba-technical@lists.samba.org>,
Namjae Jeon <linkinjeon@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: patches to move ksmbd and cifs under new subdirectory
Date: Mon, 22 May 2023 13:20:52 -0400 [thread overview]
Message-ID: <adb68fab-f251-90d3-afca-e67b77414abb@talpey.com> (raw)
In-Reply-To: <CAH2r5msVBGuRbv2tEuZWLR6_pSNNaoeihx=CjvgZ7NxwCNqZvA@mail.gmail.com>
On 5/22/2023 12:33 PM, Steve French wrote:
> Following up on the email thread suggestion to move fs/ksmbd and
> fs/cifs and fs/smbfs_common all under a common directory fs/smb, here
> is an updated
> patchset for that (added one small patch).
>
>
> 1) smb3: move Documentation/filesystems/cifs to
> Documentation/filesystems/smb
> As suggested by Namjae, update the directory for ksmbd/cifs.ko
> Documentation.
> Documentation/filesystems/cifs contains both server and client information
> so its pathname is misleading. In addition, the directory fs/smb
> now contains both server and client, so move Documentation/filesystems/cifs
> to Documentation/filesystems/smb
>
> Suggested-by: Namjae Jeon <linkinjeon@kernel.org>
>
> 2) cifs: correct references in Documentation to old fs/cifs path
> The fs/cifs directory has moved to fs/smb/client, correct mentions
> of this in Documentation and comments.
>
> 3) smb: move client and server files to common directory fs/smb
> As suggested by Linus, move CIFS/SMB3 related client and server
> files (cifs.ko and ksmbd.ko and helper modules) to new fs/smb subdirectory:
>
> fs/cifs --> fs/smb/client
> fs/ksmbd --> fs/smb/server
> fs/smbfs_common --> fs/smb/conmon
There's a typo "conmon" here, which is also present in the changelog.
The "git mv" in the patch is correct.
Regarding the fs/smb/Kconfig, curious why "CIFS" selects SMB_CLIENT?
There's no need to bring in the client in a server-only config.
Or, did this mean to be SMBFS to bring in fs/smb/common instead?
Or, maybe it's time to do away with the "CIFS" option entirely?
config CIFS
tristate "SMB3 and CIFS support (advanced network filesystem)"
depends on INET
+ select SMB_CLIENT <-- ??
select NLS
select CRYPTO
select CRYPTO_MD5
Either way, is this second SMB_CLIENT=y in fs/smb/Kconfig a typo? Should
it be =m?
+config SMBFS
+ tristate
+ default y if CIFS=y || SMB_CLIENT=y || SMB_SERVER=y
+ default m if CIFS=m || SMB_CLIENT=y <-- ? || SMB_SERVER=m
Tom.
next prev parent reply other threads:[~2023-05-22 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 16:33 Steve French
2023-05-22 17:20 ` Tom Talpey [this message]
2023-05-22 17:33 ` Linus Torvalds
2023-05-23 6:39 ` Steve French
2023-05-23 17:34 ` Linus Torvalds
2023-05-24 2:41 ` Steve French
2023-05-24 4:27 ` Steve French
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=adb68fab-f251-90d3-afca-e67b77414abb@talpey.com \
--to=tom@talpey.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®