| 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
| ||
|
Date: Mon, 20 Nov 2017 15:50:09 +0000 From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...nel.org Subject: [Bug 151491] free space lossage on busy system with bigalloc enabled and 128KB cluster https://bugzilla.kernel.org/show_bug.cgi?id=151491 --- Comment #12 from Eric Whitney (enwlinux@...il.com) --- After many attempts, I'm unable to reproduce the newly reported behavior for the delalloc workaround in comment 11 on my x86-64 test system (which is not an xfstests-bld test appliance) running either a current 4.14 kernel or an older Debian Jessie 4.8 kernel. I consistently get a reported value of 10240 1k units, which is correct for the reported size. However, in the process of running my trials I arrived at a simpler reproducer that should be helpful in identifying the source of the original space reporting problem. There's no need to copy the first test file if the test system's free memory is sufficiently limited relative to the size of the test file - a simple sequential write of a single test file suffices. In fact, the tighter the free memory, the more likely the problem occurs and the likelihood of larger reporting errors increases. A test system with ample free memory won't exhibit the problem at all. I'm getting workable kernel traces with the simpler reproducer, and the free memory-related behavior suggests a direction, so I'll see where that takes me. -- You are receiving this mail because: You are watching the assignee of the bug.
Powered by blists - more mailing lists