linux-ext4 - [Bug 201685] ext4 file system corruption

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-201685-13602-QWuoDTDERH@https.bugzilla.kernel.org/>
Date:   Sun, 02 Dec 2018 19:17:31 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 201685] ext4 file system corruption

https://bugzilla.kernel.org/show_bug.cgi?id=201685

Michael Duell (reg@...rei.me) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |reg@...rei.me

--- Comment #157 from Michael Duell (reg@...rei.me) ---
I have had file system corruption with 4.19 on a BTRFS file system as well.
4.19.2 Kernel. I think this has to be related. No files were actually corrupted
but the Kernel set the file system read-only as soon as the error occurred.

I have even tried a NEW and FRESH btrfs file system created via a LiveCD system
and it happened there as well as soon as I did a btrfs send/receive operation.

I am on a Thinkpad T450.

lspci -vvv 
https://paste.pound-python.org/show/9tZLWlry0Iy7Z629VPea/

-- 
You are receiving this mail because:
You are watching the assignee of the bug.