[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21de1dd8-b491-8c59-e874-6834978f1e2e@nod.at>
Date: Sat, 7 Jan 2017 23:40:15 +0100
From: Richard Weinberger <richard@....at>
To: Theodore Ts'o <tytso@....edu>, Eric Biggers <ebiggers3@...il.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
jaegeuk@...nel.org, hch@...radead.org, arnd@...db.de,
dedekind1@...il.com, linux-mtd@...ts.infradead.org,
adrian.hunter@...el.com, linux-ext4@...r.kernel.org,
ebiggers@...gle.com, rdunlap@...radead.org, david@...ma-star.at
Subject: Re: [PATCH v2] fscrypt: Factor out bio specific functions
Ted,
Am 07.01.2017 um 20:24 schrieb Theodore Ts'o:
> On Wed, Jan 04, 2017 at 12:10:43PM -0800, Eric Biggers wrote:
>>
>> I thought you're supposed to be able to build the kernel no matter how it's
>> configured. If this patch is really too large for 4.10 then perhaps we should
>> make FS_ENCRYPTION select CONFIG_BLOCK instead?
>
> We already have FS_ENCRYPTIOn depending on BLOCK, so this is *not*
> fixing a build break.
Kconfig is tricky. We face a build error with CONFIG_BLOCK=n with UBIFS_FS_ENCRYPTION enabled.
UBIFS file encryption does "select FS_ENCRYPTION" just like ext4 and f2fs.
This will enable ENCRYPTION even when no block support is available.
I can make UBIFS depend on BLOCK as intermediate fix.
But the real fix is this patch.
Thanks,
//richard
--
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
Powered by blists - more mailing lists