mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Wakko Warner <wakko@animx.eu.org>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Neil Brown <neilb@suse.de>
Subject: Re: [PATCH] nfsd: v4 support requires CRYPTO
Date: Mon, 6 Jun 2011 18:41:31 -0400	[thread overview]
Message-ID: <20110606224131.GE1151@fieldses.org> (raw)
In-Reply-To: <20110606112217.9648b8ff.randy.dunlap@oracle.com>

On Mon, Jun 06, 2011 at 11:22:17AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> nfsd V4 support uses crypto interfaces, so select CRYPTO
> to fix build errors in 2.6.39:

Thanks, applying for 3.0.--b.

> 
> ERROR: "crypto_destroy_tfm" [fs/nfsd/nfsd.ko] undefined!
> ERROR: "crypto_alloc_base" [fs/nfsd/nfsd.ko] undefined!
> 
> Reported-by: Wakko Warner <wakko@animx.eu.org>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: stable@kernel.org
> ---
>  fs/nfsd/Kconfig |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- linux-2.6.39.orig/fs/nfsd/Kconfig
> +++ linux-2.6.39/fs/nfsd/Kconfig
> @@ -82,6 +82,7 @@ config NFSD_V4
>  	select NFSD_V3
>  	select FS_POSIX_ACL
>  	select SUNRPC_GSS
> +	select CRYPTO
>  	help
>  	  This option enables support in your system's NFS server for
>  	  version 4 of the NFS protocol (RFC 3530).

      reply	other threads:[~2011-06-06 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 17:45 2.6.39 nfsd and crypto =n Wakko Warner
2011-06-06 18:22 ` [PATCH] nfsd: v4 support requires CRYPTO Randy Dunlap
2011-06-06 22:41   ` J. Bruce Fields [this message]

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=20110606224131.GE1151@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=randy.dunlap@oracle.com \
    --cc=wakko@animx.eu.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®