linux-ext4 - different defaults in mke2fs.conf vs. the code itself?

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

Date:	Wed, 04 Oct 2006 12:37:02 -0500
From:	Eric Sandeen <esandeen@...hat.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: different defaults in mke2fs.conf vs. the code itself?

from mke2fs.conf in 1.39:

[defaults]
        base_features = sparse_super,filetype,resize_inode,dir_index
        blocksize = 4096

and yet (for example) in PRS():

        if (blocksize <= 0) {
                profile_get_integer(profile, "defaults", "blocksize", 0,
                                    1024, &use_bsize);
                profile_get_integer(profile, "fs_types", fs_type,
                                    "blocksize", use_bsize, &use_bsiz

So the code itself defaults to 1k blocks, but the shipped config file
defaults to 4k blocks?  We noticed this when mke2fs.conf went missing
from the install environment, and formatting large filesystems took a
-very- long time.

Shouldn't these match?  Or for that matter, why should the shipped
config file be either overriding or re-stating defaults in the code
itself?  Seems a bit strange to me.

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