gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gzip (Debian) |
Fix Released
|
Unknown
|
|||
gzip (Ubuntu) |
Fix Released
|
Undecided
|
dan purdy | ||
Bionic |
Fix Released
|
Low
|
Dan Streetman |
Bug Description
[impact]
gzip/libgzip fails for systemd services using MemoryDenyWrite
[test case]
note this only fails on ppc64el
create service file /etc/systemd/
[Service]
MemoryDenyWrite
ExecStart=
run systemctl daemon-reload, and start the service:
ubuntu@
ubuntu@
ubuntu@
○ test-localegen.
Loaded: loaded (8;;file:
Active: inactive (dead)
Jun 24 16:44:18 test-ppc-b locale-gen[2737]: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted
Jun 24 16:44:18 test-ppc-b locale-gen[2738]: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted
Jun 24 16:44:18 test-ppc-b locale-gen[2739]: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted
Jun 24 16:44:18 test-ppc-b locale-gen[2740]: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted
Jun 24 16:44:18 test-ppc-b locale-gen[2741]: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted
Jun 24 16:44:18 test-ppc-b locale-gen[2506]: failed to set locale!
Jun 24 16:44:18 test-ppc-b locale-gen[2506]: [error] default character map file `ANSI_X3.4-1968' not found: No such file or directory
Jun 24 16:44:18 test-ppc-b locale-gen[2489]: done
Jun 24 16:44:18 test-ppc-b locale-gen[2483]: Generation complete.
Jun 24 16:44:18 test-ppc-b systemd[1]: test-localegen.
[regression potential]
as this sets NO_ASM any regression would likely involve changed performance or architecture-
[racb] As NO_ASM switches code implementations inside gzip, it's possible that this regresses behaviour if a bug exists in the C implementation but not in the assembly implementation. However in mitigation the C implementation has been in use since Focal, and it doesn't look like anything relevant to this change has been changed since Bionic.
[scope]
this is needed only in b
this was fixed in debian at version 1.9-2.1, so this is fixed already in f and later
Changed in gzip (Ubuntu): | |
status: | New → Fix Released |
Changed in gzip (Ubuntu Bionic): | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Dan Streetman (ddstreet) |
description: | updated |
Changed in gzip (Debian): | |
status: | Unknown → Fix Released |
description: | updated |
Changed in gzip (Ubuntu): | |
assignee: | nobody → dan purdy (purdydan317) |
> [impact]
> gzip/libgzip fails for systemd services using MemoryDenyWrite Execute= yes
Please could you expand on this? Under what circumstances are users going to be affected by this?
Specifically our SRU process requires: "An explanation of the bug on users and justification for backporting the fix to the stable release".
I also don't understand what's going on here, so I'd also appreciate "In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug".