[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170107192406.56p7ppbdfkjii4vy@thunk.org>
Date: Sat, 7 Jan 2017 14:24:06 -0500
From: Theodore Ts'o <tytso@....edu>
To: Eric Biggers <ebiggers3@...il.com>
Cc: Richard Weinberger <richard@....at>, 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
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.
Given that, it's a bit harder to claim this is a must-have bug fix for
the stable branch?
- Ted
Powered by blists - more mailing lists