linux-ext4 - Incompatibility between mballoc and online resize

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-next>] [day] [month] [year] [list]

Date:	Mon, 09 Jun 2008 23:46:00 -0400
From:	"Theodore Ts'o" <tytso@....edu>
To:	Alex Tomas <alex.tomas@....com>, Andreas Dilger <adilger@....com>
cc:	linux-ext4@...r.kernel.org
Subject: Incompatibility between mballoc and online resize

I've been trying to track down the problems in ext4's online-resizing,
and one of the ones which is most noticeable is that online resizing
mballoc has some specific data structures which need to be enlarged when
the number of block groups in the filesystem are grown dynamically.

Specifically, the s_group_info array; in the current ext4 patch queue,
this isn't happening, which means after the online resizing operation,
when the filesystem is unmounted, ext4_put_super() calls
ext4_mb_release(), which then iterates over s_group_info array, and then
this triggers a kernel oops.

Is clusterfs running with mballoc in production?  If so, how was this
problem fixed?  Did we miss a patch to make sure that on-line resizing
worked with mballoc enabled?

Thanks, regards,

						- Ted
--
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