From: Michael Guntsche <mike@it-loops.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>, kwc@umich.edu
Subject: Re: [BUG] supported_krb5_enctypes not available if GSS support compiled as a module
Date: Wed, 20 Apr 2011 23:59:59 +0200 [thread overview]
Message-ID: <20110420235654@it-loops.com> (raw)
In-Reply-To: <20110420213906.GB24503@pad.home.fieldses.org>
On 20 Apr 11 17:39, J. Bruce Fields wrote:
> On Wed, Apr 20, 2011 at 10:49:51PM +0200, Michael Guntsche wrote:
> > Hello Bruce,
> >
> > Commit 0a5e5f122c nfsd: fix compile error fixed a compile error by
> > putting the code between an #ifdef CONFIG_SUNRPC_GSS.
> >
> > In my case this is compiled as a module so CONFIG_SUNRPC_GSS_MODULE is
> > defined but not CONFIG_SUNRPC_GSS. I do not know if this was on purpose
> > but as it is now "supported_krb5_enctypes" is only available if GSS
> > support is compiled in the kernel.
>
> Ugh, fuzzy thinking on my part.
>
> So I guess to do this right we want modules to be able to dynamically
> add files to the nfsd filesystem at module load time?
This seems to be working already. The problem is that CONFIG_SUNRPC_GSS
is not defined when configured as a module so the code is not being
built in the first place. I tested this by defining CONFIG_SUNRPC_GSS at
the beginning of the file.
Of course you can test for both CONFIG_SUNRPC_GSS AND *GSS_MODULE but I
do not know if this is the correct way.
/Michael
next prev parent reply other threads:[~2011-04-20 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 20:49 [BUG] supported_krb5_enctypes not available if GSS support compiled as a module Michael Guntsche
2011-04-20 21:39 ` J. Bruce Fields
2011-04-20 21:59 ` Michael Guntsche [this message]
2011-04-21 6:24 ` Michael Guntsche
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=20110420235654@it-loops.com \
--to=mike@it-loops.com \
--cc=bfields@redhat.com \
--cc=kwc@umich.edu \
--cc=linux-nfs@vger.kernel.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