linux-ext4 - Re: [PATCH 2/2] ext4: don't allow r/w mounts if metadata blocks overlap the superblock

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

Message-ID: <DM5PR2101MB1032A56161CBF73A94B72C36FBA10@DM5PR2101MB1032.namprd21.prod.outlook.com>
Date:   Fri, 30 Mar 2018 16:16:06 +0000
From:   Sasha Levin <Alexander.Levin@...rosoft.com>
To:     Sasha Levin <Alexander.Levin@...rosoft.com>,
        Theodore Ts'o <tytso@....edu>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>
CC:     Theodore Ts'o <tytso@....edu>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH 2/2] ext4: don't allow r/w mounts if metadata blocks
 overlap the superblock

Hi EXT4 ML!

I'm working on a project to perform automatic patch selection for
stable, and automate the testing being done for patches going in
various stable tree.

I got some input from the XFS folks so far, and wanted to get some
input from the EXT4 folks as well.

Below is a mail that would be sent as a response for ext4 patches
tagged for stable and sent to the mailing list. Since this one is
already tagged for stable, these results should be useful for people
to understand if the patch properly applies to various stable trees
and passes testing.

For EXT4, at this point testing is the xfstests tree at
https://github.com/tytso/xfstests , running with "./check -g auto".
Complete build and test logs are available in the links embedded in
the mail.

I'd be happy to get feedback for this. Thanks!

===

Hi Theodore Ts'o,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has also determined it's probably a bug fixing patch. (score: 90.6059)

The bot has tested the following trees: v4.15.12, v4.14.29, v4.9.89, v4.4.123, v4.1.50, v3.18.101.

v4.15.12: Build OK!
v4.14.29: Build OK!
v4.9.89: Build failed! Errors:
    fs/ext4/super.c:2263:9: error: implicit declaration of function ‘sb_rdonly’ [-Werror=implicit-function-declaration]

v4.4.123: Build failed! Errors:
    fs/ext4/super.c:2134:9: error: implicit declaration of function ‘sb_rdonly’ [-Werror=implicit-function-declaration]

v4.1.50: Build failed! Errors:
    fs/ext4/super.c:2129:9: error: implicit declaration of function ‘sb_rdonly’ [-Werror=implicit-function-declaration]

v3.18.101: Build failed! Errors:
    fs/ext4/super.c:2096:9: error: implicit declaration of function ‘sb_rdonly’ [-Werror=implicit-function-declaration]

EXT4 Specific tests:

v4.15.12 (http://stable-bot.westus2.cloudapp.azure.com/ext4-patch/v4.15.12/tests/):
    Tests complete.
v4.14.29 (http://stable-bot.westus2.cloudapp.azure.com/ext4-patch/v4.14.29/tests/):
    Tests complete.
v4.9.89 (http://stable-bot.westus2.cloudapp.azure.com/ext4-patch/v4.9.89/tests/):
    No tests completed!
v4.4.123 (http://stable-bot.westus2.cloudapp.azure.com/ext4-patch/v4.4.123/tests/):
    No tests completed!
v4.1.50 (http://stable-bot.westus2.cloudapp.azure.com/ext4-patch/v4.1.50/tests/):
    No tests completed!
v3.18.101 (http://stable-bot.westus2.cloudapp.azure.com/ext4-patch/v3.18.101/tests/):
    No tests completed!

Please let us know if you'd like to have this patch included in a stable tree.

--
Thanks,
Sasha