[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f820c3e8-8538-ac95-9303-eeee77c903ee@gmail.com>
Date: Mon, 23 Sep 2019 11:46:55 +0200
From: Milan Broz <gmazyland@...il.com>
To: Thibaut Sautereau <thibaut.sautereau@...p-os.org>,
Mike Snitzer <snitzer@...hat.com>, dm-devel@...hat.com,
Alasdair Kergon <agk@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [dm-devel] dm-crypt error when CONFIG_CRYPTO_AUTHENC is disabled
On 23/09/2019 10:20, Thibaut Sautereau wrote:
>
> On top of that, there's no hint in kernel logs about a particular
> algorithm, feature or Kconfig option that could be missing. Do we really
> expect people simply tuning their kernel configuration to go and read
> the source code to ensure they are not breaking their system?
AFAIK all standard Linux kernels in distros have these options enabled,
so it works out of the box.
So it is the opposite view - if you are setting your kernel options,
you need to dig much deeper...
I can perhaps add some hint to userspace if this is detectable from errno though.
Milan
Powered by blists - more mailing lists