This is hard to follow in chronological order. The summary is we thought it was a btrfs bug, then we though it was random memory corruption, then ran a debug kernel and hit crazy things constantly instead of just once every couple of weeks, then quickly found an upstream bug report.

On the one hand, this is discovered and reproduced on Fedora 40. On the other hand, the problem is isolated to the kernel, and including 6.11 series which is what Fedora 41 will ship with. I'm inferring this problem will happen on 41 (as well as 40 and 39, anything with the affected kernel versions).

FinalBlocker +1

Note: "must be fixed or documented at Common Issues"

FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

Pretty clear violation of the data corruption criteria.

I'm not sure how effective CommonBugs will be for this, most people probably wouldn't look until after the corruption has hit disk, if at all. Unfortunately not much else we can do.

FinalBlocker +1

AGREED AcceptedFinalBlocker

Discussed during the 2024-10-07 blocker review meeting [1]:

This is accepted as a conditional violation of "All known bugs that can cause corruption of user data must be fixed or documented at Common Issues", for affected AMD laptops.

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-10-07/f41-blocker-review.2024-10-07-16.00.log.html

The following votes have been closed:

• Accepted FinalBlocker (+7, 0, -0)
  • +1 by chrismurphy, ngompa, asciiwolf, geraldosimiao, nixuser, derekenz, nielsenb

Release F41 is no longer tracked by BlockerBugs, closing this ticket.