Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210517224330.9201-1-dai.ngo@oracle.com> <20210517224330.9201-2-dai.ngo@oracle.com>
 <CAN-5tyGYhmy_dgKV_7xuPFJjyY_wsjDcun_TrDK_vidmVG1ZXg@mail.gmail.com> <20210518172334.GC25205@fieldses.org>
In-Reply-To: <20210518172334.GC25205@fieldses.org>
From:   Olga Kornievskaia <olga.kornievskaia@gmail.com>
Date:   Tue, 18 May 2021 13:31:11 -0400
Message-ID: <CAN-5tyG2pcduQAWJDaP83VgqK7QfsnoDZJe-JG=Oqdgj4PjSUg@mail.gmail.com>
Subject: Re: [PATCH v5 1/2] NFSD: delay unmount source's export after
 inter-server copy completed.
To:     "J. Bruce Fields" <bfields@fieldses.org>
Cc:     Dai Ngo <dai.ngo@oracle.com>,
        linux-nfs <linux-nfs@vger.kernel.org>,
        Trond Myklebust <trondmy@hammerspace.com>,
        Chuck Lever <chuck.lever@oracle.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, May 18, 2021 at 1:23 PM J. Bruce Fields <bfields@fieldses.org> wrote:
>
> On Tue, May 18, 2021 at 01:16:56PM -0400, Olga Kornievskaia wrote:
> > General question to maybe Bruce: can nfsd_net go away while a compound
> > is using it ?
>
> No.  Any server threads for that container should be shut down before
> nfsd_net goes away.

Right, sorry but the async copy is a task that works after the
compound of copy.  You say "threads .. should be shut down", who makes
sure of that (meaning should async copy code make sure of it)?

>
> --b.