linux-kernel - Re: Does the discard bug introduced in 4.19 by 744889b7cbb56a6 and fixed by 1adfc5e4136f5967 have potential for fstrim-caused 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] [day] [month] [year] [list]

Date:   Mon, 12 Nov 2018 09:22:14 +0800
From:   Ming Lei <ming.lei@...hat.com>
To:     Vito Caputo <vcaputo@...garu.com>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>, snitzer@...hat.com,
        hch@....de, xni@...hat.com, mariusz.dabrowski@...el.com,
        axboe@...nel.dk
Subject: Re: Does the discard bug introduced in 4.19 by 744889b7cbb56a6 and
 fixed by 1adfc5e4136f5967 have potential for fstrim-caused corruption?

On Sat, Nov 10, 2018 at 12:06:35AM -0800, Vito Caputo wrote:
> I ask because I recently performed some fstrims on my 4.19-running
> laptop after a good house cleaning, and things started going rather
> haywire today at the filesystem level, on different filesystems of
> differing types (ext2 and ext4) but sharing the same underlying lvm
> pv+dmcrypt on an SSD.

Could you share us your test case? And what is the exact issue triggered
in your system?

> 
> At the time I needed to get work done and couldn't investigate.  So I
> crossed my fingers and rebooted back into 4.18, let some ugly fscks
> complete, and carried on like nothing happened.
> 
> This all seems to be a software bug, not a genuine SSD failure of any
> sort.
> 
> My filesystems are now all in a questionable state, though the machine
> seems usable enough for the moment while I prepare for rebuilding.
> 
> Should I assume this was all caused by the fstrims and 744889b7cbb56a6?

You may confirm that by revert 744889b7cbb56a6 and see if your issue is
gone.

However, 1adfc5e4136f5967d is supposed to fix 744889b7cbb56a6, so I
strongly suggest you to can verify 1adfc5e4136f5967d.

Thanks,
Ming