Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
From: Dai Ngo <dai.ngo@xxxxxxxxxx>
Date: Tue, 2 Apr 2024 14:29:23 +0000
Accept-language: en-US
Cc: Jeff Layton <jlayton@xxxxxxxxxx>, "linux-nfs@xxxxxxxxxxxxxxx" <linux-nfs@xxxxxxxxxxxxxxx>
In-reply-to: <ZgwO9/3pwOoC/qIk@tissot.1015granger.net>
References: <ZgdR48dhdSoUj+VM@tissot.1015granger.net> <09da882f-4bad-4398-a2d0-ef8daefce374@oracle.com> <ZghZzfIi5RkWDh9K@tissot.1015granger.net> <84d6311e-a0a3-4fc6-a87e-e09857c765b3@oracle.com> <039c7e38b70287541849ab03d92818740fdf5d43.camel@kernel.org> <Zgq365RJ9M5qsgWY@tissot.1015granger.net> <5108ca5a-b626-4ae9-a809-ae3fffb50cab@oracle.com> <a30b343f-b6cf-4566-9565-28a5fd5ca851@oracle.com> <ZgrzwVp4GrbmZGWt@tissot.1015granger.net> <86dd7031-744d-4448-96ed-6d3d9c2e49b0@oracle.com> <ZgwO9/3pwOoC/qIk@tissot.1015granger.net>

Unexport works fine. It was my mistake.

-Dai

> On Apr 2, 2024, at 6:58 AM, Chuck Lever III <chuck.lever@xxxxxxxxxx> wrote:
> 
> On Mon, Apr 01, 2024 at 12:55:16PM -0700, Dai Ngo wrote:
>> 
>>> On 4/1/24 10:49 AM, Chuck Lever wrote:
>>> The question I have is will this unresponsive client cause other
>>> issues, such as:
>>> 
>>>  - a hang when the server tries to unexport
>> 
>> exportfs -u does not hang, but the share can not be un-exported.
> 
> What does "can not be un-exported" mean? Does "exportfs -u" fail?
> Seems like this is a UX bug.
> 
> 
> --
> Chuck Lever

References:
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Chuck Lever
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Dai Ngo
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Chuck Lever
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Dai Ngo
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Jeff Layton
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Chuck Lever
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Dai Ngo
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Dai Ngo
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Chuck Lever
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Dai Ngo
- Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
  - From: Chuck Lever

Prev by Date: Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
Next by Date: Re: [nfs-utils PATCH] mount: reject "namlen=" option for a NFSv4 mount
Previous by thread: Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
Next by thread: Re: [PATCH 1/1] NFSD: cancel CB_RECALL_ANY call when nfs4_client is about to be destroyed
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux USB Development] [Linux Media Development] [Video for Linux] [Linux NILFS] [Linux Audio Users] [Yosemite Info] [Linux SCSI]