WeSearch
EROFS Disables LZ4 Rolling Decompression Due To Data Corruption Possibility

EROFS Disables LZ4 Rolling Decompression Due To Data Corruption Possibility

·2 min read · 0 reactions · 0 comments · 7 views
More from Phoronix tech Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

The EROFS file system has temporarily disabled its LZ4 rolling decompression feature ahead of the Linux 7.3-rc3 kernel release. This decision was made after AWS identified rare instances of data corruption caused by uncontrolled backward memory copies in the current LZ4 implementation. The change prioritizes data correctness over the memory efficiency benefits previously provided by the rolling window optimization.

Key facts
About this source

Phoronix files mainly under tech. We currently carry 340 of its stories.

Original article
Phoronix
Read full at Phoronix →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherPhoronix
Canonical URLhttps://www.phoronix.com/news/EROFS-Disabled-LZ4-Rolling
Publication timeSat, 12 Sep 2026 20:33:00 -0400
Retrieval time2026-09-13T03:16:49.663Z
Last seen2026-09-13T03:16:49.663Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster5IFfskCeXUGF · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

EROFS Disables LZ4 Rolling Decompression Due To Data Corruption Possibility Written by Michael Larabel in Linux Storage on 12 September 2026 at 08:33 PM EDT. Add A Comment The EROFS read-only file-system popular for embedded systems, containers, and other use-cases has resorted to temporarily disabling its LZ4 rolling decompression support due to data corruption concerns. Ahead of the Linux 7.3-rc3 kernel release due out on Sunday, EROFS has mid-cycle deemed it necessary to disable the LZ4 rolling data decompression capability it supported. Today's EROFS merge noted: "The most impactful fix here is to disable LZ4 rolling decompression for now.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Phoronix.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Phoronix