Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp903198ybc; Tue, 12 Nov 2019 11:02:36 -0800 (PST) X-Google-Smtp-Source: APXvYqxZ/Lz5cmp82QvnN9l/6ERHUpo3tmhtsF1N2alNZcvHM1VVJ0pIDHIp13Cq3RF2CwUnoYUC X-Received: by 2002:a17:906:a38d:: with SMTP id k13mr29673914ejz.213.1573585356616; Tue, 12 Nov 2019 11:02:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573585356; cv=none; d=google.com; s=arc-20160816; b=XaDxW4bc22D447M9NNXicQeHOV2I0ay/6YMGwb0RzY9z6JAxg+XkSFzVXVXFJJgYp7 42Ox073qt+4j6+eLRi1TyUJ8vPR4Op6ieL89CRtYpcwFYRC0eHESsHhPzarucn36uxxw Qw7OuxqH9xMWKhGOt2McmvyK+az71fxi0P7TapgdmFRb8pAy0BezAQY6peQVeuijVSSq YUsI218mdEOGOBoHAnYk+2C3wjH/KbYJja4hhM7tyLY56toPDqMk78o0UyyW9Fj3uEEx 1cR7PEu1CpvxUSjt3uIkGpCH9z46A3B7mFUWCLt/2NZV13d/qytsBCWEPgyzUouBlYNI ZTgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:message-id:date :subject:cc:to:from:dkim-signature; bh=1feI9EKUPd44UXi5eUrQQI0QVVdtYSwR1BfGPNKxR9E=; b=e3M1H/HmFG3+IPB0X41Fudm8V6d84xC/mdakfEl47q0UEgO+n5eNB8ig7VrNGYHZsv zy9D6S3zA96N5CDvQpUxmw5kWBAjQqKdM/I0b95XgoxE5qBBOriJeD0EGTC9jseS0/Cs JC1EQe0hEdwnALT4sD/pfCHVGf4h9Kpyg8q5Nra/Vf2RYvnAKoPkRs+sFDVkA7J9wjMW 5JJb4wyGKhaclwdGLPI8adNafCcB/M7LnpqzsG6AfkhaZ9oJB/rss1Hn6b+eYcTiWn1K GTMQFoklH0BJjORxOKv7KYAdX98GP1YD9hx586w0Y8z5C2VfGt7G5o1m0HZxHqpA8/DG nLhw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="gF7/yjjX"; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cb6si566412ejb.359.2019.11.12.11.02.06; Tue, 12 Nov 2019 11:02:36 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="gF7/yjjX"; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726973AbfKLTCB (ORCPT + 99 others); Tue, 12 Nov 2019 14:02:01 -0500 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:52417 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726952AbfKLTCB (ORCPT ); Tue, 12 Nov 2019 14:02:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573585320; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=1feI9EKUPd44UXi5eUrQQI0QVVdtYSwR1BfGPNKxR9E=; b=gF7/yjjXuB9h5Q8e5Fr4aiBMhUpm707uz9nwS8zODlUHBfwUvLu1ySFx39yr5NjHwbrg/5 KfwhQItb6nPUN5sDkqEAYDZAIW63+MMqonz/aMk12puAvZQ2odmvcO5WsYKEWLda0UXYhM PHCw1D1nnFeh7JvtYT6wJIZFB0Xxru4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-250-cw4tKdJ-MCa5xGptBklOsQ-1; Tue, 12 Nov 2019 14:01:57 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8818C101AEF5; Tue, 12 Nov 2019 19:01:56 +0000 (UTC) Received: from coeurl.usersys.redhat.com (ovpn-122-210.rdu2.redhat.com [10.10.122.210]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1D25B1891F; Tue, 12 Nov 2019 19:01:56 +0000 (UTC) Received: by coeurl.usersys.redhat.com (Postfix, from userid 1000) id BF48B208EC; Tue, 12 Nov 2019 14:01:55 -0500 (EST) From: Scott Mayhew To: bfields@fieldses.org, chuck.lever@oracle.com Cc: jamie@audible.transient.net, linux-nfs@vger.kernel.org Subject: [PATCH] nfsd: v4 support requires CRYPTO_SHA256 Date: Tue, 12 Nov 2019 14:01:55 -0500 Message-Id: <20191112190155.12872-1-smayhew@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: cw4tKdJ-MCa5xGptBklOsQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org The new nfsdcld client tracking operations use sha256 to compute hashes of the kerberos principals, so make sure CRYPTO_SHA256 is enabled. Fixes: 6ee95d1c8991 ("nfsd: add support for upcall version 2") Reported-by: Jamie Heilman Signed-off-by: Scott Mayhew --- fs/nfsd/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig index 10cefb0c07c7..c4b1a89b8845 100644 --- a/fs/nfsd/Kconfig +++ b/fs/nfsd/Kconfig @@ -73,7 +73,7 @@ config NFSD_V4 =09select NFSD_V3 =09select FS_POSIX_ACL =09select SUNRPC_GSS -=09select CRYPTO +=09select CRYPTO_SHA256 =09select GRACE_PERIOD =09help =09 This option enables support in your system's NFS server for --=20 2.17.2