Bug #16457
Building feature/buster in RAM sometimes fails: mksquashfs reaped by OOM killer
0%
Description
For context, initial analysis, and test results, see Bug #16177.
Next steps:
- Verify that squashfs-tools 4.3-3.0tails4 does honor
-mem
consistently (I think I did already but let’s be sure). - Find out why squashfs-tools 4.3-11 does not honor
-mem
consistently, e.g.:- Try to reproduce with pristine 4.3-3 changes
- Try reverting the 4.3-3..4.3-11 changes
- Try applying the patchset collected by lynxis on top of 4.3-11
- Report the bug, ideally with a patch attached.
Subtasks
Related issues
Related to Tails - |
Resolved | 2018-12-02 | |
Related to Tails - |
Resolved | ||
Blocks Tails - Feature #16209: Core work: Foundations Team | Confirmed |
History
#1 Updated by intrigeri 2019-02-11 15:55:34
- blocks Feature #16209: Core work: Foundations Team added
#2 Updated by intrigeri 2019-02-11 15:55:47
- Description updated
#3 Updated by intrigeri 2019-02-11 15:55:57
- Subject changed from Building ISO in RAM sometimes fails: mksquashfs reaped by OOM killer to Building feature/buster in RAM sometimes fails: mksquashfs reaped by OOM killer
#4 Updated by intrigeri 2019-02-11 15:56:13
- related to
Bug #16177: Building ISO in RAM often fails: mksquashfs reaped by OOM killer added
#5 Updated by intrigeri 2019-03-18 18:24:55
#6 Updated by lamby 2019-03-18 18:27:06
This is https://bugs.debian.org/923711
Mon 18 14:22 <@lamby> Looks like something that could be handled under FT.
Mon 18 14:23 <@lamby> If so, I'll file an issue in Redmine
Mon 18 14:23 <======> lamby: I'd think so
#7 Updated by lamby 2019-03-18 18:27:25
- Assignee set to lamby
#8 Updated by anonym 2019-04-02 20:05:57
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|6370ba62f331a6c715cbcdb625f4b9a5f7af13a4.
#9 Updated by lamby 2019-04-04 10:55:18
This was fixed in:
squashfs-tools (1:4.3-12) unstable; urgency=medium
.
[ Alexander Couzens <lynxis@fe80.eu> ]
* Fix compressor initialization in frag_deflator() (closes: #923711).
I’m going to request an unblock for buster.
#10 Updated by lamby 2019-04-04 11:10:30
Asked the maintainer whether I can ask for an unblock ask. https://bugs.debian.org/923711#98
#11 Updated by intrigeri 2019-04-05 13:00:21
- Type of work changed from Research to Wait
#12 Updated by lamby 2019-04-05 16:39:29
- Status changed from In Progress to Resolved
1:4.3-12 was uploaded to sid:
https://tracker.debian.org/news/1036885/accepted-squashfs-tools-143-12-source-into-unstable/
and was unblocked for buster:
https://tracker.debian.org/news/1037397/squashfs-tools-143-12-migrated-to-testing/
Resolving to match.
#13 Updated by intrigeri 2019-04-05 16:41:33
- Status changed from Resolved to In Progress
> 1:4.3-12 was uploaded to sid […] and was unblocked for buster:
Woohoo!
> Resolving to match.
I think we’ll need to revert commit:6370ba62f331a6c715cbcdb625f4b9a5f7af13a4 in order to switch to this new, unblocked version (otherwise we’re stuck with a temporary workaround).
#14 Updated by intrigeri 2019-04-05 16:43:24
- Assignee deleted (
lamby) - Type of work changed from Wait to Code
#15 Updated by lamby 2019-04-05 16:48:53
@intrigeri https://salsa.debian.org/tails-team/tails/merge_requests/7
#16 Updated by intrigeri 2019-04-05 16:57:20
- Target version changed from Tails_3.14 to Tails_4.0
#17 Updated by intrigeri 2019-04-05 17:00:06
- Assignee set to intrigeri
#18 Updated by intrigeri 2019-04-05 17:11:18
- QA Check set to Ready for QA
#19 Updated by intrigeri 2019-04-05 17:42:39
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - QA Check changed from Ready for QA to Pass
#20 Updated by intrigeri 2019-04-06 16:39:05
- related to
Bug #16637: squashfs-tools from Buster (1:4.3-12) is much slower than 1:4.3-8.0tails1 added