linux-kernel - Re: linux-next: Tree for Dec 15 (fs/ubifs/ causes problems in fs/crypto/)

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

Message-ID: <ac59de6f-eaac-d088-a9d7-ce77e10f8a51@nod.at>
Date:   Thu, 15 Dec 2016 23:46:02 +0100
From:   Richard Weinberger <richard@....at>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        linux-next@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        Artem Bityutskiy <dedekind1@...il.com>,
        linux-mtd@...ts.infradead.org, Eric Biggers <ebiggers@...gle.com>,
        Theodore Ts'o <tytso@....edu>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: linux-next: Tree for Dec 15 (fs/ubifs/ causes problems in
 fs/crypto/)

Randy,

On 15.12.2016 19:13, Randy Dunlap wrote:
> On 12/14/16 19:21, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any material for v4.11 to your linux-next included
>> branches until after v4.10-rc1 has been released.
>>
>> Changes since 20161214:
>>
> 
> on x86_64:
> 
> when CONFIG_BLOCK is not enabled:
> 
> warning: (UBIFS_FS_ENCRYPTION) selects FS_ENCRYPTION which has unmet direct dependencies (BLOCK)

UBIFS does not depend on CONFIG_BLOCK but fs/crypto/ does.
As short-term solution we can make UBIFS_FS_ENCRYPTION depend on CONFIG_BLOCK,
a better solution would be extracting all block specific stuff from fs/crypto/crypto.c
to another file.

Thanks,
//richard