linux-kernel - Re: ext2/zram issue [was: Linux 5.19]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <a3544988-5503-ae0e-3c66-a75019b673c0@kernel.org>
Date:   Wed, 31 Aug 2022 09:55:56 +0200
From:   Jiri Slaby <jirislaby@...nel.org>
To:     charlie39@...k.li
Cc:     adilger.kernel@...ger.ca, jack@...e.com,
        linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
        minchan@...nel.org, ngupta@...are.org, senozhatsky@...omium.org,
        torvalds@...ux-foundation.org, tytso@....edu
Subject: Re: ext2/zram issue [was: Linux 5.19]

On 30. 08. 22, 23:46, charlie39@...k.li wrote:
> Hi, I think i bumped on  the same issue on version 5.19.2 with ext4 on zram mounted on /tmp

Only 5.19.6 contains the fix.

> ```
> # sudo dmesg -T | grep ext4
> 
> [Tue Aug 30 21:41:45 2022] EXT4-fs error (device zram1): ext4_check_bdev_write_error:218: comm kworker/u8:3: Error while
> [Tue Aug 30 21:41:45 2022] EXT4-fs warning (device zram1): ext4_end_bio:347: I/O error 10 writing to inode 76 starting b
> [Tue Aug 30 21:41:45 2022] EXT4-fs warning (device zram1): ext4_end_bio:347: I/O error 10 writing to inode 76 starting b
> [Tue Aug 30 21:41:45 2022] EXT4-fs warning (device zram1): ext4_end_bio:347: I/O error 10 writing to inode 66 starting b
> [Tue Aug 30 22:07:02 2022] EXT4-fs error (device zram1): ext4_journal_check_start:83: comm ThreadPoolForeg: Detected abo
> [Tue Aug 30 22:07:02 2022] EXT4-fs (zram1): Remounting filesystem read-only
> 
> ```
> Not sure what caused it, i was just updating my arch system.
> 

-- 
js