On Thu, 2022-01-20 at 14:55 -0300, Andreas Hasenack wrote: > Hi again, > > On Thu, Jan 20, 2022 at 10:16 AM Andreas Hasenack > <andreas@xxxxxxxxxxxxx> wrote: > > Something still feels wrong, though, and behaves differently from > > 5.1.7. > > > > I applied all your patches for 5.1.8, even unrelated ones, and > > tried this: > > # this would trigger the segfault in plain 5.1.8: > > root@j-s390x:~# time ls -la /cifs/localhost/private > > total 4 > > drwxr-xr-x 2 root root 0 Dec 27 20:15 . > > drwxr-xr-x 5 root root 0 Jan 20 13:03 .. > > -rwxr-xr-x 1 root root 64 Jan 19 13:02 hello-private.txt > > > > real 0m0.130s > > user 0m0.000s > > sys 0m0.001s > > root@j-s390x:~# time ls -la /cifs/localhost/pub > > total 4 > > drwxr-xr-x 2 root root 0 Dec 27 20:15 . > > drwxr-xr-x 5 root root 0 Jan 20 13:03 .. > > -rwxr-xr-x 1 root root 63 Jan 19 13:02 hello-public.txt > > > > real 0m0.014s > > user 0m0.001s > > sys 0m0.001s > > > > # This is expected to fail, because I only have > > /etc/creds/localhost, > > not /etc/creds/127.0.0.1 > > root@j-s390x:~# time ls -la /cifs/127.0.0.1/private > > ls: cannot access '/cifs/127.0.0.1/private': No such file or > > directory > > > > real 0m0.075s > > user 0m0.000s > > sys 0m0.001s > > > > # but this hangs, and ls process goes into D state. With 5.1.7 it > > works. > > root@j-s390x:~# time ls -la /cifs/127.0.0.1/pub > > <hangs> > > The above hang happens for me when patch 5 is applied: [PATCH 05/19] > autofs-5.1.8 - fix root offset error handling > > In summary, for my s390x case: > - [PATCH 05/19] autofs-5.1.8 - fix root offset error handling: > introduces the hang in the above scenario > - [PATCH 08/19] autofs-5.1.8 - fix loop under run in > cache_get_offset_parent(): fixes the s390x segfault, and failure to > mount the private cifs share Thanks for you efforts on this problem. The patch 5 introducing a hang is interesting, I'll have to have a look at that. Thanks Ian
