LATX: Scope KZT compatibility fallback by library group - #398
Merged
LaurenIsACoder merged 1 commit intoAug 14, 2026
Merged
Conversation
Compatibility checks previously disabled the process-wide KZT option when an application path contained a private guest library matching any wrapped SONAME. This also disabled unrelated library families, while wrapper-selection logs could still describe the configured groups rather than the execution-time result. Keep the configured mask as the requested state and prune incompatible families only from a separate effective mask. Derive the execution-time KZT predicate from the process-level 0/1/2 mode and the effective mask, then use it consistently for translation, bridge, signal, address-validation, relocation, and callback paths. Configuration, direct-exec, and Wine deferral continue to manage the process-level mode. Match private guest libraries at the .so boundary and confirm each candidate is an x86_64 ELF. Remove the undocumented GTK3/libXt name gate; retain the existing Chrome process gate as an explicit all-family rejection. Signed-off-by: Hanlu Li <heuleehanlu@gmail.com>
LaurenIsACoder
marked this pull request as ready for review
August 14, 2026 07:53
Contributor
|
Loongnix Desktop ABI 1.0 gtkperf-for-gtk3开启LATX_KZT_LIBS=cairo符合预期。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
KZT compatibility fallback was process-wide. When an application search path contained a private x86_64 library matching any wrapped SONAME,
CheckEnableKZT()disabled the global KZT mode. The same global fallback was also hard-coded for GTK3 and libXt dependencies.This made one library conflict disable unrelated KZT library groups. It also left execution-time KZT hooks controlled only by the process-level mode, even when no library group remained usable.
Change
.soboundary and verify that candidates are x86_64 ELF files.Validation
git diff --check origin/master...HEADscripts/checkpatch.pl --no-treereports 0 errorsThe normal LoongArch product build and integration tests have not yet been run.