On Thu, Jun 07, 2012 at 03:40:40PM -0700, Kees Cook wrote: > > FWIW, I was building the filesystem that triggered this as ext4: > > mkfs.ext4 -T default -m 0 -O ^huge_file,^flex_bg -E > discard,lazy_itable_init /dev/mapper/... Ouy of curiosity, was there a reason you chose those particular file system parameters? It's a surprising set, because if you're starting with a fresh file system, enabling flex_bg produces a more optimal file system layout. The reason why I wrote the commit description way I did was because it seemed to be the most likely way that someone would trip across this bug. We didn't notice this for as long as we did since most of the users of ext4 (especially those who use community distributions) have been using freshly mkfs'ed ext4 file systems. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
