All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "François Valenduc" <francoisvalenduc@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, stable@vger.kernel.org
Subject: Re: Linux 4.14.36
Date: Tue, 24 Apr 2018 14:50:20 +0200	[thread overview]
Message-ID: <20180424125020.GA3514@kroah.com> (raw)
In-Reply-To: <3c50e8af-ea15-fc56-18be-419c27b7844e@gmail.com>

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@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
> 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

  reply	other threads:[~2018-04-24 12:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24  9:20 Linux 4.14.36 Greg KH
2018-04-24  9:21 ` Greg KH
2018-04-24 11:52 ` François Valenduc
2018-04-24 12:31   ` Greg KH
2018-04-24 12:40     ` François Valenduc
2018-04-24 12:50       ` Greg KH [this message]
2018-04-24 14:19         ` François Valenduc
2018-04-24 15:09     ` Theodore Y. Ts'o
2018-04-24 18:17       ` François Valenduc
2018-04-24 20:25         ` Theodore Y. Ts'o
2018-04-25 20:05           ` François Valenduc
2018-04-26  5:44             ` Greg KH
2018-04-26  6:35               ` Greg KH
2018-04-26  6:22             ` Theodore Y. Ts'o
2018-04-26 11:36               ` François Valenduc
2018-04-26 17:05                 ` Theodore Y. Ts'o
2018-04-26 17:22                   ` Greg KH
2018-04-26 21:00                     ` Theodore Y. Ts'o
2018-04-26 13:42               ` James Blanford
2018-04-26 14:50               ` James Blanford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180424125020.GA3514@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=francoisvalenduc@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.