stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Blanford <jhblanford@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: "François Valenduc" <francoisvalenduc@gmail.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: Linux 4.14.36
Date: Thu, 26 Apr 2018 08:50:06 -0600	[thread overview]
Message-ID: <20180426085006.701104e8@anima.localnet.prv> (raw)
In-Reply-To: <20180426062250.GG18803@thunk.org>


BTW, I get the opposite results from François on my Debian system when
I build all three crc32c drivers as modules:

jim@anima:/lib/modules/4.14.36-test2$ find . -name "*crc32c*"

./kernel/lib/libcrc32c.ko
./kernel/arch/x86/crypto/crc32c-intel.ko
./kernel/crypto/crc32c_generic.ko

crc32c_generic and crc32c_intel are added to the initrd, but libcrc32c
is not.

lsinitramfs /boot/initrd.img-4.14.36-test2|grep crc32

lib/modules/4.14.36-test2/kernel/arch/x86/crypto/crc32c-intel.ko
lib/modules/4.14.36-test2/kernel/crypto/crc32c_generic.ko

On Thu, 26 Apr 2018 02:22:51 -0400
"Theodore Y. Ts'o" <tytso@mit.edu> wrote:

> François, James,
> 
> Does this fix things for you?
> 
> Thanks,
> 
> 					- Ted
> 
> From 7ef79ad52136712172eb0525bf0b462516bf2f93 Mon Sep 17 00:00:00 2001
> From: Theodore Ts'o <tytso@mit.edu>
> Date: Thu, 26 Apr 2018 00:44:46 -0400
> Subject: [PATCH] ext4: add MODULE_SOFTDEP to ensure crc32c is
> included in the initramfs MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> Fixes: a45403b51582 ("ext4: always initialize the crc32c checksum
> driver") Reported-by: François Valenduc <francoisvalenduc@gmail.com>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Cc: stable@vger.kernel.org
> ---
>  fs/ext4/super.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 185f7e61f4cf..eb104e8476f0 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -5886,5 +5886,6 @@ static void __exit ext4_exit_fs(void)
>  MODULE_AUTHOR("Remy Card, Stephen Tweedie, Andrew Morton, Andreas
> Dilger, Theodore Ts'o and others"); MODULE_DESCRIPTION("Fourth
> Extended Filesystem"); MODULE_LICENSE("GPL");
> +MODULE_SOFTDEP("pre: crc32c");
>  module_init(ext4_init_fs)
>  module_exit(ext4_exit_fs)


-- 
#DeleteFacebook

      parent reply	other threads:[~2018-04-26 14: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
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 [this message]

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=20180426085006.701104e8@anima.localnet.prv \
    --to=jhblanford@gmail.com \
    --cc=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).