| 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
| ||
|
Message-ID: <BAY179-W85AF983234DB78F07A12EFDB50@phx.gbl> Date: Sat, 20 Sep 2014 16:46:36 -0400 From: TR Reardon <thomas_reardon@...mail.com> To: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org> Subject: resize2fs problem with stride calc resize2fs seems to come up with some crazy default stride numbers. This occurs with and without bigalloc. I was testing enabling/disabling 64bit using latest patches from DJW, and noticed that s_raid_stride was being written with nonsensical values, in particular determine_fs_stride() is coming up with overly large values. The code is old (2006) and lacks comment so I'm not sure what the intended operation is. Does this just need to be updated for flex_bg? Should s_raid_stride ever be auto-changed on resize? If it should change, should stripe also change? +Reardon -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists