Control: tag -1 upstream On Friday, 3 June 2022 09:53:41 CEST Michael Schaller wrote: > Note that on kernel 5.17 we also see this error in the kernel log: > [ 24.206158] I/O error, dev loop0, sector 32640 op 0x0:(READ) flags > 0x80700 phys_seg 1 prio class 0 On Friday, 3 June 2022 13:58:03 CEST Michael Schaller wrote: > I've tested some vanilla stable kernels (without Debian patches) and > can confirm that 5.17.0 and 5.18.1 (latest) are affected. Kernel > 5.16.18 isn't affected. > > a git bisect pointed towards this commit as the first bad commit: > https://github.com/torvalds/linux/commit/1ebe2e5f9d68e94c524aba876f27b945669a7879 https://lore.kernel.org/all/20211122130625.1136848-12-hch@lst.de/ is linked in that commit and a recent reply points to sth similar as you see: https://lore.kernel.org/all/Yo4+zEnrBTnoEMCz@T590/ If you agree, then it seems to me that the best course of action seems to get involved in that discussion.
Attachment:
signature.asc
Description: This is a digitally signed message part.