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-1loCj9thhE@https.bugzilla.kernel.org/>
Date:   Fri, 30 Nov 2018 14:20:59 +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

--- Comment #87 from Artem S. Tashkinov (aros@....com) ---
Regression testing could be carried out in a VM running on top of a ramdisk
(e.g. tmpfs) to speed up the process.

I guess someone with a decent amount of persistence and spare time could do
that and test each individual commit between 4.18 and 4.19, however that
doesn't guarantee success since the bug might be hardware related and not
reproducible in a virtual environment. Or it might require obscene amounts of
RAM/disk space which would be difficult, if not impossible to reproduce in a
VM.

I for one decided to stay on 4.18.x and not upgrade to any more recent kernels
until the regression is identified and dealt with.

Maybe one day someone will become truly invested in the kernel development
process and we'll have proper QA/QC/unit testing/regression testing/fuzzying,
so that individuals won't have to sacrifice their data and time because kernel
developers are mostly busy with adding new features and usually not really
concerned with performance, security and stability of their code unless they
are pointed at such issues.

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