stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "François Valenduc" <francoisvalenduc@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: Linux 4.14.36
Date: Wed, 25 Apr 2018 22:05:23 +0200	[thread overview]
Message-ID: <50bfaae2-60db-ddac-46bf-aedbec1f1951@gmail.com> (raw)
In-Reply-To: <20180424202534.GA7925@thunk.org>



Le 24/04/18 à 22:25, Theodore Y. Ts'o a écrit :
> On Tue, Apr 24, 2018 at 08:17:23PM +0200, François Valenduc wrote:
>> I am using gentoo and indeed, the crc32_generic  module was not included
>> in the initramfs by default. I have added it and now I can use the
>> 4.14.36 kernel without having to revert this commit.
> So Gentoo doesn't automatically figure out which modules are required
> based on module depndencies (e.g., from the modules.dep file)?
>
> That seems like a... bug.  If this is a problem which is widespread
> across distributions, then we might have many more users running into
> this when 4.17 and the latest stable kernels get rolled out.
>
>      	       	       	      	     	     - Ted
I think that gentoo take into account modules dependencies. For example,
jbd2 is included automatically in the initramfs without having to
specifially include via the modules_load file of the genkernel package:

grep jbd2 /usr/share/genkernel/arch/x86_64/modules_load
zsh: exit 1     grep --colour=auto jbd2
/usr/share/genkernel/arch/x86_64/modules_load

and jbd2 is also specified as a dependency for ext4 in the modules.dep file:

grep jbd2 modules.dep                                 
kernel/fs/ext4/ext4.ko: kernel/fs/mbcache.ko kernel/fs/jbd2/jbd2.ko
kernel/fs/jbd2/jbd2.ko:

but the crc32_generic module is not listed as a dependency for ext4:

 grep crc32 modules.dep                                
kernel/crypto/crc32c_generic.ko:
kernel/drivers/md/persistent-data/dm-persistent-data.ko:
kernel/lib/libcrc32c.ko kernel/drivers/md/dm-bufio.ko
kernel/drivers/md/dm-mod.ko kernel/drivers/dax/dax.ko
kernel/drivers/md/dm-thin-pool.ko:
kernel/drivers/md/persistent-data/dm-persistent-data.ko
kernel/lib/libcrc32c.ko kernel/drivers/md/dm-bio-prison.ko
kernel/drivers/md/dm-bufio.ko kernel/drivers/md/dm-mod.ko
kernel/drivers/dax/dax.ko
kernel/lib/libcrc32c.ko:

So, would this be the cause of the problem ?

François Valenduc

  reply	other threads:[~2018-04-25 20:05 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 [this message]
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=50bfaae2-60db-ddac-46bf-aedbec1f1951@gmail.com \
    --to=francoisvalenduc@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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).