Received-SPF: pass (google.com: domain of linux-nfs+bounces-912-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Message-ID: <9fc4294f-4fb9-45b7-a4e8-7243f075ea16@redhat.com>
Date: Wed, 3 Jan 2024 19:38:37 -0500
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH 0/6] nfs-utils: handle BAD_INTEGRITY ERROR
Content-Language: en-US
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>
Cc: linux-nfs@vger.kernel.org, chuck.lever@oracle.com
References: <20231206213332.55565-1-olga.kornievskaia@gmail.com>
From: Steve Dickson <steved@redhat.com>
In-Reply-To: <20231206213332.55565-1-olga.kornievskaia@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


On 12/6/23 4:33 PM, Olga Kornievskaia wrote:
> From: Olga Kornievskaia <kolga@netapp.com>
> 
> This patch series is re-work of the previous patch series that handles
> gss error for bad integrity. In this version, gssd is changed to use
> rpc_gss_seccreate() function in tirpc which exposes the gss errors to
> the caller. This functionality is further checked with configure for the
> presence of this function in the tirpc library.
> 
> Note that the current libtirpc (1.3.4 version) needs a fix to
> rpc_gss_seccreate() to work correctly for the gssd that passes in
> credentials to be used for the gss context establishement.
> 
> Olga Kornievskaia (6):
>    gssd: revert commit a5f3b7ccb01c
>    gssd: revert commit 513630d720bd
>    gssd: switch to using rpc_gss_seccreate()
>    gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for machine credentials
>    gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for user credentials
>    configure: check for rpc_gss_seccreate
> 
>   aclocal/libtirpc.m4    |  5 +++++
>   utils/gssd/gssd_proc.c | 26 +++++++++++++++++++++++---
>   2 files changed, 28 insertions(+), 3 deletions(-)
> 
Committed... (tag: nfs-utils-2-7-1-rc3)

steved.