Latest Debian 12 LTS images have a kernel crash
Comments on “Latest Debian 12 LTS images have a kernel crash”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Timon de Groot reports on the Debian LTS list that bookworm kernel 6.1.192-1 (DLA-4906-1) causes ext4 NULL-pointer oopses on some OpenStack VMs, typically during large dpkg installs, after which writes block in jbd2 until reboot. He attributes it to mballoc folio backports from 6.1.191, where IS_ERR() checks miss the NULL that 6.1's filemap_get_folio() returns. The diagnosis is his own and unverified. Another project saw the oops on 6.1.191 and mentions a queued fix he could not locate. He pins packages to the earlier kernel.
Why it ranked
No. 13 of 122 with a score of 0.67. The panel rated it highest on technical depth (0.89) and substantiated (0.83), lowest on audience breadth (0.58). Placed No. 13, No. 22 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- A detailed bug report of a Debian LTS kernel regression causing ext4 oopses and journal hangs in production VMs, with bisect history and a workaround. Substantive and practically relevant to infrastructure operators, but narrow in scope.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported, technically detailed Debian kernel regression report with reproducible symptoms, stack traces, suspected backported patches, and a workaround. It matters directly to Linux operators, though its scope is narrower than a general kernel vulnerability or release.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.67total under rubric v2.3
- Significance0.60
- Reader interest0.72
- Audience breadth0.58
- Practical relevance0.74
- Substantiated0.83
- Technical depth0.89
- New information0.82
- Counts against: Promotional0.02
- Counts against: Overclaim0.17
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.61 | 0.55 | 0.65 | 0.60 | 0.10 | +0.24 | +0.145 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.63 | 0.70 | 0.82 | 0.72 | 0.19 | +0.26 | +0.186 |
| Audience breadthHow many people who build technology does it concern? | 0.59 | 0.60 | 0.55 | 0.58 | 0.05 | +0.13 | +0.075 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.65 | 0.80 | 0.78 | 0.74 | 0.15 | +0.22 | +0.164 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.90 | 0.70 | 0.90 | 0.83 | 0.20 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 0.98 | 0.80 | 0.88 | 0.89 | 0.18 | +0.05 | +0.044 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.60 | 0.96 | 0.82 | 0.36 | +0.05 | +0.041 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.02 | 0.00 | 0.02 | 0.04 | −0.19 | −0.004 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.32 | 0.15 | 0.04 | 0.17 | 0.28 | −0.11 | −0.019 |
| Sum of contributions | +0.674 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.674 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-17/13/"><img src="https://rubric.hrih.si/badge/2026-11-17/13.svg" alt="Ranked #13 on Rubric, 17 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 5 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenCausal conclusion
Debian bookworm kernel 6.1.192-1 (DLA-4906-1) causes ext4 oopses on bookworm VMs, after which every write to the affected filesystem blocks in jbd2 until reboot.
The article gives no link or citation for it.
The article says “Since 6.1.192-1 (DLA-4906-1) we get ext4 oopses on bookworm VMs”
The source says No source to compare with.
No source givenGeneralization
The reporter did not see the oops on the previous bookworm-security kernel.
The article gives no link or citation for it.
The article says “We didn't see it on the previous bookworm-security kernel”
The source says No source to compare with.
No source givenVersion
Kernel 6.1.191 brought in mballoc backports converting bd_bitmap_page and bd_buddy_page to folios, plus a fix for e4b bitmap inconsistency reports (CVE-2026-45942).
The article gives no link or citation for it.
The article says “6.1.191 brought in these mballoc backports”
The source says No source to compare with.
No source givenCausal conclusion
On kernel 6.1, __filemap_get_folio() returns NULL rather than an ERR_PTR, so the backport's IS_ERR() checks do not catch the failure, causing the NULL dereference.
The article gives no link or citation for it.
The article says “On 6.1, __filemap_get_folio() returns NULL rather than an ERR_PTR, so the IS_ERR() checks from the backport don't catch it”
The source says No source to compare with.
Couldn’t checkDate
The same set of patches was dropped from 6.1.167-rc1 in March after Mark Brown bisected an identical oops and Ted Ts'o reproduced it on x86_64.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The same set of patches was dropped from 6.1.167-rc1 in March, after Mark Brown bisected an identical oops and Ted Ts'o reproduced it on x86_64”
The source says No passage could be compared.
Source cited by the article: lkml.iu.edu/2603.3/01511.html
No source givenVersion
The patches came back in 6.1.191.
The article gives no link or citation for it.
The article says “It came back with 6.1.191”
The source says No source to compare with.
Matches sourceNumber
Another project hit the same oops on 6.1.191 and mentions a 6.1.y fix queued upstream that is not in 6.1.192.
The cited source says the same thing.
The article says “Another project ran into the same oops on 6.1.191 and mentions a 6.1.y fix being queued upstream that isn't in 6.1.192”
The source says “The upstream 6.1.y fix is queued but not in 6.1.192”
Source cited by the article: github.com/sporevm/kernels/pull/13
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.