linux-ext4 - Problem with data=ordered ext4 mount option in linux-next

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]

Message-ID: <b5817114-8122-cf0e-ca8e-b5d1c9f43bc2@gmail.com>
Date:   Fri, 17 Dec 2021 16:11:32 +0100
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Lukas Czerner <lczerner@...hat.com>, linux-ext4@...r.kernel.org,
        linux-fsdevel@...r.kernel.org
Subject: Problem with data=ordered ext4 mount option in linux-next

On linux-next systemd-remount-fs complains about an invalid mount option
here, resulting in a r/o root fs. After playing with the mount options
it turned out that data=ordered causes the problem. linux-next from Dec
1st was ok, so it seems to be related to the new mount API patches.

At a first glance I saw no obvious problem, the following looks good.
Maybe you have an idea where to look ..

static const struct constant_table ext4_param_data[] = {
	{"journal",	EXT4_MOUNT_JOURNAL_DATA},
	{"ordered",	EXT4_MOUNT_ORDERED_DATA},
	{"writeback",	EXT4_MOUNT_WRITEBACK_DATA},
	{}
};

	fsparam_enum	("data",		Opt_data, ext4_param_data),