[OpenAFS-devel] Android studio hangs openafs

[Mark Vitale]

Markus,

> On Aug 30, 2021, at 1:18 PM, markus.suvanto@gmail.com wrote:
>=20
> ma, 2021-08-30 kello 02:14 +0000, Mark Vitale kirjoitti:
>>=20
>> Lastly, if none of these shed light on the issue, please
>> obtain a kernel backtrace while the problem is occurring:
>>=20
>> # echo t > /proc/sysrq-trigger
>>=20
> kernel config, openafs config.log and journalctl (sysrq-trigger stuff) ar=
e here:
> https://drive.google.com/drive/folders/1ZiQInTxJlxLLebij2f9jMgBT6LaiUUnB?=
usp=3Dsharing
>=20
Thank you!  From the journalctl, here's the relevant task backtrace, edited=
 for clarity:

elo 30 19:46:22 t470.station.com kernel: task:ApplicationImpl state:S stack=
:    0 pid: 2286 ppid:  1785 flags:0x00004000

elo 30 19:46:22 t470.station.com kernel: Call Trace:
elo 30 19:46:22 t470.station.com kernel:  __schedule+0x254/0x12d0
elo 30 19:46:22 t470.station.com kernel:  schedule+0x3f/0xa0
elo 30 19:46:22 t470.station.com kernel:  afs_osi_SleepSig+0xfe/0x1e0 [liba=
fs]
elo 30 19:46:22 t470.station.com kernel:  afs_osi_Sleep+0x46/0x70 [libafs]
elo 30 19:46:22 t470.station.com kernel:  afs_LookupAFSDB+0x150/0x2a0 [liba=
fs]
elo 30 19:46:22 t470.station.com kernel:  afs_lookup+0x13fc/0x1b60 [libafs]
elo 30 19:46:22 t470.station.com kernel:  afs_linux_lookup+0x79/0x330 [liba=
fs]
elo 30 19:46:22 t470.station.com kernel:  __lookup_slow+0x7f/0x150
elo 30 19:46:22 t470.station.com kernel:  walk_component+0x14f/0x1d0
elo 30 19:46:22 t470.station.com kernel:  path_lookupat+0x69/0x1b0
elo 30 19:46:22 t470.station.com kernel:  filename_lookup+0xc6/0x1d0
elo 30 19:46:22 t470.station.com kernel:  vfs_statx+0x6d/0x110

This shows the AFS client waiting for completion of DNS cell name lookup (A=
FSDB/SRV records).
The best way forward is to do a packet trace of the DNS traffic, then dupli=
cate the
problem to see what cell name we are trying to look up.  Most likely it wil=
l either
be a real cell with a typo in the name, or it will be a metadata file that =
is not a cell name
at all.

Regards,
--
Mark Vitale
mvitale@sinenomine.net