Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From:   "NeilBrown" <neilb@suse.de>
To:     "Trond Myklebust" <trondmy@hammerspace.com>,
        Muchun Song <songmuchun@bytedance.com>
Cc:     "sebastian.fricke@collabora.com" <sebastian.fricke@collabora.com>,
        "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Possible NFS4 regression on 5.18-rc1
In-reply-to: <23f11c6151f9bbfbb09d2699f4388d4a09a87127.camel@hammerspace.com>
References: <20220406142541.eouf7ryfbd7aooye@basti-XPS-13-9310>,
 <23f11c6151f9bbfbb09d2699f4388d4a09a87127.camel@hammerspace.com>
Date:   Thu, 07 Apr 2022 10:38:07 +1000
Message-id: <164929188775.10985.17822469281433754130@noble.neil.brown.name>
Precedence: bulk

On Thu, 07 Apr 2022, Trond Myklebust wrote:
> On Wed, 2022-04-06 at 16:25 +0200, Sebastian Fricke wrote:
> > [You don't often get email from sebastian.fricke@collabora.com. Learn
> > why this is important at
> > http://aka.ms/LearnAboutSenderIdentification.]
> >=20
> > Hello folks,
> >=20
> > I am currently developing a V4L2 driver with support on GStreamer,
> > for
> > that purpose I am mounting the GStreamer repository via NFS from my
> > development machine to the target ARM64 hardware.
> >=20
> > I just switched to the latest kernel and got a sudden hang up of my
> > system.
> > What I did was a rebase of the GStreamer repository and then I wanted
> > to
> > build it with ninja on the target, this failed with a segmentation
> > fault:
> > ```
> > gstreamer| Configuring libgstreamer-1.0.so.0.2100.0-gdb.py using
> > configurat=3D
> > ion
> > Segmentation fault
....

> > [ 4595.209552] pc : list_lru_add+0xd4/0x180
> > [ 4595.209907] lr : list_lru_add+0x15c/0x180

This is almost certainly fixed by the patch at

https://lore.kernel.org/all/164876616694.25542.14010655277238655246@noble.nei=
l.brown.name/

which almost landed in -mm, but didn't quite.

The subsequent email

https://lore.kernel.org/all/CAMZfGtUMyag7MHxmg7E1_xmyZ7NDPt62e-qXbqa8nJHFC72=
=3D3w@mail.gmail.com/

suggests a one-line change.

Trond: maybe you could queue this?

NeilBrown