On Tue, Apr 24, 2018 at 02:40:18PM +0200, François Valenduc wrote: > > > Le 24/04/18 à 14:31, Greg KH a écrit : > > 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@xxxxxxx> > >> 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@xxxxxxx> > >> Cc: stable@xxxxxxxxxxxxxxx > >> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > >> > >> 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 > I can't know if 4.17-rc2 has the same problem, because it doesn't boot > for another reason. It hangs while loading the initrd image. Could that be the same reason? Did 4.17-rc1 work for you? thanks, greg k-h