I started seeing the same problem when I rebased on rc1, and the suggested patch fixes it for me. Anna On Wed, Apr 6, 2022 at 11:23 PM Muchun Song <songmuchun@xxxxxxxxxxxxx> wrote: > > On Thu, Apr 7, 2022 at 8:38 AM NeilBrown <neilb@xxxxxxx> wrote: > > > > 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@xxxxxxxxxxxxx. Learn > > > > why this is important at > > > > http://aka.ms/LearnAboutSenderIdentification.] > > > > > > > > Hello folks, > > > > > > > > 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. > > > > > > > > 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= > > > > 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@xxxxxxxxxxxxxxxxxxxxx/ > > > > which almost landed in -mm, but didn't quite. > > > > The subsequent email > > > > https://lore.kernel.org/all/CAMZfGtUMyag7MHxmg7E1_xmyZ7NDPt62e-qXbqa8nJHFC72=3w@xxxxxxxxxxxxxx/ > > > > suggests a one-line change. > > > > Trond: maybe you could queue this? > > > Hi NeilBrown, > > The complete patch could be found here. Please > queue this one. > > [1] https://lore.kernel.org/all/20220401025905.49771-1-songmuchun@xxxxxxxxxxxxx/ > > Thanks.
