From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "François Valenduc" <francoisvalenduc@gmail.com>,
"James Blanford" <jhblanford@gmail.com>,
stable@vger.kernel.org
Subject: Re: Linux 4.14.36
Date: Thu, 26 Apr 2018 17:00:16 -0400 [thread overview]
Message-ID: <20180426210016.GE5965@thunk.org> (raw)
In-Reply-To: <20180426172249.GC18087@kroah.com>
On Thu, Apr 26, 2018 at 07:22:49PM +0200, Greg KH wrote:
>
> Given that this has not really been reported much, I'm tending to think
> that either the distros all have it correct, or that people have it
> correct in their configurations.
>
> I don't even use an initrd, and this all worked "just fine" for me,
> perhaps that is because I do not build ext4 as a module?
Yes, if you don't build ext4 as a module, then crc32c will be
built-into the kernel as well, and the problem won't occur. What
worries me is that most people building custom kernels generally will
build in the modules that they need, since it is the optimal thing to
do. It will be those who build ext4 and crc32c as a module, and use
an ext4 root file system, that will be hit by this.
> Anyway, let's see if we get any more reports before worrying too much.
> Thanks for the deep dive into Debian bug history :)
If we get reports, we should try to get what distro's they are
running, since it's probably going to be distro-dependent. Hopefully,
I'm worrying over nothing. :-)
- Ted
next prev parent reply other threads:[~2018-04-26 22:28 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
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 [this message]
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=20180426210016.GE5965@thunk.org \
--to=tytso@mit.edu \
--cc=francoisvalenduc@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhblanford@gmail.com \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).