BPF related reboots

[Inevitable-Phoenix]

Hello,

Upon upgrading from 22 to 23, it looks like something has changed because now I'm getting reboots related to my outdated BPF kernel. I patched my kernel in the past which worked wonderfully on 22, but 23 seems to have broken it again. I'm just curious if anyone has any insight? It reboots upon installing/uninstalling/archiving/restoring apps. It looks like it's related to eBPF networking layer null pointer during package lifecycle events, just odd it wasn't an issue before on 22 or maybe less of an issue. I also get some random reboots but that's less of an issue.

Also, I just wanted to say thank you for putting out this rom.

Thank you

[stelios333]

Having random reboots on my Samsung a22 5g (kernel 4.14.186-27218697) too after upgrading to Lineageos 23.0. Looking through the adb logs, confirms the error is exactly what you're describing:

01-10 20:10:56.401 30480 30720 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityServiceThread
01-10 20:10:56.401 30480 30720 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.PACKAGE_REMOVED dat=package: flg=0x4000010 (has extras) } in android.net.connectivity.com.android.server.connectivity.PermissionMonitor$1@ade180
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1847)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.app.LoadedApk$ReceiverDispatcher$Args.$r8$lambda$mcNAAl1SQ4MyJPyDg8TJ2x2h0Rk(Unknown Source:0)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:995)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:103)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.os.Looper.loopOnce(Looper.java:248)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:338)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.os.HandlerThread.run(HandlerThread.java:85)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.net.connectivity.com.android.net.module.util.IBpfMap.deleteEntry(android.net.connectivity.com.android.net.module.util.Struct)' on a null object reference
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.net.connectivity.com.android.server.BpfNetMaps.removeUidFromLocalNetBlockMap(BpfNetMaps.java:1074)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.net.connectivity.com.android.server.connectivity.PermissionMonitor.onPackageRemoved(PermissionMonitor.java:918)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.net.connectivity.com.android.server.connectivity.PermissionMonitor$1.onReceive(PermissionMonitor.java:183)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1839)
01-10 20:10:56.401 30480 30720 E AndroidRuntime: 	... 7 more

Unfortunately I don't have any idea either on what the root cause could be although my (probably incorrect) theory is that android's code has started becoming incompatible with the outdated kernels of our phones. I rolled back to lineageos 22.1 for now and haven't had any random reboots so far.\

I'm curious @MisterZtr, do you face the same issues too with your phones or is it device-specific?

[nels83]

I'm having the same symptoms/logs on a Galaxy Tab A8. I've never tried downgrading to lineageos 22 so I can't tell if it's new.

[Inevitable-Phoenix]

I found the frequency of my random reboots dropped to almost never when I disabled Google Play Store. I make use of the private space feature and found that I could leave the private space Google Play enabled and it would still keep the random reboots to almost never. I haven't done any more trouble shooting than that though, but likely the vanilla version of this rom won't have this issue.