From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:57516 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751264AbeDXMby (ORCPT
        <rfc822;stable@vger.kernel.org>); Tue, 24 Apr 2018 08:31:54 -0400
Date: Tue, 24 Apr 2018 14:31:48 +0200
From: Greg KH <gregkh@linuxfoundation.org>
To: =?iso-8859-1?Q?Fran=E7ois?= Valenduc <francoisvalenduc@gmail.com>,
        Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org
Subject: Re: Linux 4.14.36
Message-ID: <20180424123148.GA20848@kroah.com>
References: <20180424092056.GA24237@kroah.com>
 <71965e45-04de-8772-87ee-3497bff8b89a@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <71965e45-04de-8772-87ee-3497bff8b89a@gmail.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Tue, Apr 24, 2018 at 01:52:19PM +0200, Fran�ois Valenduc wrote:
 > 
> This version doens't boot on my computer. I am using gentoo with an
> encrypted root partition using ext4. After that I have entered the
> password, the root partition can not be mounted. I have bisected it to
> the following commit:
> 
> commit 26dbb30c58ffb85bc015bd5e58831483d50f7d18
> Author: Theodore Ts'o <tytso@mit.edu>
> Date:   Thu Mar 29 22:10:31 2018 -0400
> 
>     ext4: always initialize the crc32c checksum driver
> 
>     commit a45403b51582a87872927a3e0fc0a389c26867f1 upstream.
> 
>     The extended attribute code now uses the crc32c checksum for hashing
>     purposes, so we should just always always initialize it.  We also want
>     to prevent NULL pointer dereferences if one of the metadata checksum
>     features is enabled after the file sytsem is originally mounted.
> 
>     This issue has been assigned CVE-2018-1094.
> 
>     https://bugzilla.kernel.org/show_bug.cgi?id=199183
>     https://bugzilla.redhat.com/show_bug.cgi?id=1560788
> 
>     Signed-off-by: Theodore Ts'o <tytso@mit.edu>
>     Cc: stable@vger.kernel.org
>     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Indeed, if I revert this commit, the problem doesn't occur. 4.16.4 also
> fails to boot, probably for the same reason, since this commit is also
> included.
> 
> Does anybody know what is happening ?

That's really odd.  Do we not have "enough" randomness at boot time?
Does 4.17-rc2 also fail in this same way?

Ted, any ideas?

thanks,

greg k-h