Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 14 Jun 2022 06:00:21 +0900
From:   Dominique Martinet <asmadeus@codewreck.org>
To:     Tyler Hicks <tyhicks@linux.microsoft.com>
Cc:     Christian Schoenebeck <linux_oss@crudebyte.com>,
        v9fs-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/06] fid refcounting improvements and fixes
Message-ID: <YqelZWe4BJfDkYEd@codewreck.org>
References: <20220612085330.1451496-1-asmadeus@codewreck.org>
 <20220613202053.GI7401@sequoia>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20220613202053.GI7401@sequoia>
Precedence: bulk

Tyler Hicks wrote on Mon, Jun 13, 2022 at 03:20:53PM -0500:
> On 2022-06-12 17:53:23, Dominique Martinet wrote:
> > @@ -222,7 +221,8 @@ static struct p9_fid *v9fs_fid_lookup_with_uid(struct dentry *dentry,
> >                  * We need to hold rename lock when doing a multipath
> >                  * walk to ensure none of the patch component change
> >                  */
> > -               fid = p9_client_walk(old_fid, l, &wnames[i], clone);
> > +               fid = p9_client_walk(old_fid, l, &wnames[i],
> > +                                    old_fid == root_fid /* clone */);
> 
> This is no problem at all. The rebased patches look good to me. Squash
> your fix to my fix and it should be ready to go.

Thanks for all your reviews :)
I've rebased my branch if you want to check:
https://github.com/martinetd/linux/commits/9p-next

We've just started a cycle so I'll submit the first three patches (fixes
to stable) next week, and the rest for when 5.20 cycle starts.
Feel free to remind me if it looks like I forgot.
-- 
Dominique