Linux NFS development
 help / color / mirror / Atom feed
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: Wed, 13 Feb 2008 13:58:54 -0500	[thread overview]
Message-ID: <20080213185854.GF13462@fieldses.org> (raw)
In-Reply-To: <47B336CD.2020305@oracle.com>

On Wed, Feb 13, 2008 at 01:28:29PM -0500, Chuck Lever wrote:
> J. Bruce Fields wrote:
>> 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?
>
> It appears that the "select RPCSEC_GSS_KRB5" is a no-op if  
> RPCSEC_GSS_KRB5 hasn't met it's forward dependencies.

Oh, OK, I didn't understand that.

However, this means that it's no longer possible to build a V4 client
with krb5 support without also including PROC_FS.  So I think we can't
apply this as is.

--b.

  reply	other threads:[~2008-02-13 18:59 UTC|newest]

Thread overview: 14+ 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
2008-02-13 18:28         ` Chuck Lever
2008-02-13 18:58           ` J. Bruce Fields [this message]
  -- 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

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=20080213185854.GF13462@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox