From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@fys.uio.no, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 07/11] NFSD: Use "depends on" for PROC_FS dependency
Date: Tue, 12 Feb 2008 17:30:20 -0500 [thread overview]
Message-ID: <20080212223020.GO18625@fieldses.org> (raw)
In-Reply-To: <9C44C93A-AC87-4B21-8E31-872186ABCEBB@oracle.com>
On Tue, Feb 12, 2008 at 05:10:57PM -0500, Chuck Lever wrote:
>
> On Feb 12, 2008, at 4:23 PM, J. Bruce Fields wrote:
>
>> On Mon, Feb 11, 2008 at 05:12:16PM -0500, Chuck Lever wrote:
>>> Recently, commit 440bcc59 added a reverse dependency to fs/Kconfig to
>>> ensure that PROC_FS was enabled if NFSD_V4 was enabled.
>>>
>>> There is a guideline in Documentation/kbuild/kconfig-language.txt
>>> that
>>> states "In general use select only for non-visible symbols (no
>>> prompts
>>> anywhere) and for symbols with no dependencies."
>>>
>>> A quick grep around other Kconfig files reveals that no entry
>>> currently
>>> uses "select PROC_FS" -- every one uses "depends on". Thus
>>> CONFIG_NFSD_V4
>>> should use "depends on PROC_FS" as well.
>>
>> OK.
>>
>>>
>>> For SUNRPC_GSS, it's a little more complex. Other entries can
>>> "select"
>>> SUNRPC_GSS, as it is non-visible. However, the guideline suggests an
>>> entry can't "select" it if it has a dependency (such as PROC_FS).
>>> So, we add forward dependencies on PROC_FS to RPCSEC_GSS_FOO instead.
>>
>> This also makes the client dependent on PROC_FS, which it wasn't
>> before.
>>
>> I assume nobody cares?
>
> Huh? If I disable PROC_FS, I can still select the NFS client options,
> even NFSv4.
OK. I'm confused, then:
NFS_V4 selects RPCSEC_GSS_KRB5
RPCSEC_GSS_KRB5 (after this patch) depends on PROC_FS
What am I missing?
--b.
>
>>> XXX: Both CONFIG_NFSV4 and CONFIG_NFSD_V4 select RPCSEC_GSS_KRB5,
>>> which is
>>> visible, which kconfig-language.txt also frowns upon. The intent
>>> was to
>>> enable at least one GSS mechanism if V4 was enabled. Perhaps we
>>> should
>>> make SUNRPC_GSS visible, and make the NFSv4 options visible only if
>>> SUNRPC_GSS is enabled.
>>>
>>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>>> ---
>>>
>>> fs/Kconfig | 8 +++-----
>>> 1 files changed, 3 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/fs/Kconfig b/fs/Kconfig
>>> index 0c8f85d..9ee288f 100644
>>> --- a/fs/Kconfig
>>> +++ b/fs/Kconfig
>>> @@ -1662,8 +1662,6 @@ config NFSD
>>> select CRYPTO_MD5 if NFSD_V4
>>> select CRYPTO if NFSD_V4
>>> select FS_POSIX_ACL if NFSD_V4
>>> - select PROC_FS if NFSD_V4
>>> - select PROC_FS if SUNRPC_GSS
>>> help
>>> Choose Y here if you want to allow other computers to access
>>> files residing on this system using Sun's Network File System
>>> @@ -1723,7 +1721,7 @@ config NFSD_V3_ACL
>>>
>>> config NFSD_V4
>>> bool "NFS server support for NFS version 4 (EXPERIMENTAL)"
>>> - depends on NFSD && NFSD_V3 && EXPERIMENTAL
>>> + depends on NFSD && NFSD_V3 && PROC_FS && EXPERIMENTAL
>>> select RPCSEC_GSS_KRB5
>>> help
>>> This option enables support in your system's NFS server for
>>> @@ -1798,7 +1796,7 @@ config SUNRPC_BIND34
>>>
>>> config RPCSEC_GSS_KRB5
>>> tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)"
>>> - depends on SUNRPC && EXPERIMENTAL
>>> + depends on SUNRPC && PROC_FS && EXPERIMENTAL
>>> select SUNRPC_GSS
>>> select CRYPTO
>>> select CRYPTO_MD5
>>> @@ -1817,7 +1815,7 @@ config RPCSEC_GSS_KRB5
>>>
>>> config RPCSEC_GSS_SPKM3
>>> tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)"
>>> - depends on SUNRPC && EXPERIMENTAL
>>> + depends on SUNRPC && PROC_FS && EXPERIMENTAL
>>> select SUNRPC_GSS
>>> select CRYPTO
>>> select CRYPTO_MD5
>>>
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
>
>
next prev parent reply other threads:[~2008-02-12 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 22:12 [PATCH 07/11] NFSD: Use "depends on" for PROC_FS dependency Chuck Lever
[not found] ` <20080211221216.1047.31922.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-02-12 21:23 ` J. Bruce Fields
2008-02-12 21:47 ` Trond Myklebust
[not found] ` <1202852836.9228.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-12 22:32 ` J. Bruce Fields
2008-02-12 22:57 ` Trond Myklebust
[not found] ` <1202857069.9228.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-13 18:22 ` Chuck Lever
2008-02-13 18:44 ` Chuck Lever
2008-02-13 21:48 ` Trond Myklebust
2008-02-12 22:10 ` Chuck Lever
2008-02-12 22:30 ` J. Bruce Fields [this message]
2008-02-13 18:28 ` Chuck Lever
2008-02-13 18:58 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 17:52 Chuck Lever
[not found] ` <20080208175215.16261.39243.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-02-08 20:22 ` Sam Ravnborg
2008-02-08 20:22 ` Sam Ravnborg
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=20080212223020.GO18625@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.