Patch "module: statically initialize init section freeing data" has been added to the 5.8-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a note to let you know that I've just added the patch titled

    module: statically initialize init section freeing data

to the 5.8-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     module-statically-initialize-init-section-freeing-da.patch
and it can be found in the queue-5.8 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit 25ef7d34d8d0829a821aabfc010465b6431ec50a
Author: Daniel Jordan <daniel.m.jordan@xxxxxxxxxx>
Date:   Thu Oct 8 13:32:20 2020 -0400

    module: statically initialize init section freeing data
    
    [ Upstream commit fdf09ab887829cd1b671e45d9549f8ec1ffda0fa ]
    
    Corentin hit the following workqueue warning when running with
    CRYPTO_MANAGER_EXTRA_TESTS:
    
      WARNING: CPU: 2 PID: 147 at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0
      Modules linked in: ghash_generic
      CPU: 2 PID: 147 Comm: modprobe Not tainted
          5.6.0-rc1-next-20200214-00068-g166c9264f0b1-dirty #545
      Hardware name: Pine H64 model A (DT)
      pc : __queue_work+0x3b8/0x3d0
      Call trace:
       __queue_work+0x3b8/0x3d0
       queue_work_on+0x6c/0x90
       do_init_module+0x188/0x1f0
       load_module+0x1d00/0x22b0
    
    I wasn't able to reproduce on x86 or rpi 3b+.
    
    This is
    
      WARN_ON(!list_empty(&work->entry))
    
    from __queue_work(), and it happens because the init_free_wq work item
    isn't initialized in time for a crypto test that requests the gcm
    module.  Some crypto tests were recently moved earlier in boot as
    explained in commit c4741b230597 ("crypto: run initcalls for generic
    implementations earlier"), which went into mainline less than two weeks
    before the Fixes commit.
    
    Avoid the warning by statically initializing init_free_wq and the
    corresponding llist.
    
    Link: https://lore.kernel.org/lkml/20200217204803.GA13479@Red/
    Fixes: 1a7b7d922081 ("modules: Use vmalloc special flag")
    Reported-by: Corentin Labbe <clabbe.montjoie@xxxxxxxxx>
    Tested-by: Corentin Labbe <clabbe.montjoie@xxxxxxxxx>
    Tested-on: sun50i-h6-pine-h64
    Tested-on: imx8mn-ddr4-evk
    Tested-on: sun50i-a64-bananapi-m64
    Reviewed-by: Eric Biggers <ebiggers@xxxxxxxxxx>
    Signed-off-by: Daniel Jordan <daniel.m.jordan@xxxxxxxxxx>
    Signed-off-by: Jessica Yu <jeyu@xxxxxxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/kernel/module.c b/kernel/module.c
index 08c46084d8cca..991395d60f59c 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -91,8 +91,9 @@ EXPORT_SYMBOL_GPL(module_mutex);
 static LIST_HEAD(modules);
 
 /* Work queue for freeing init sections in success case */
-static struct work_struct init_free_wq;
-static struct llist_head init_free_list;
+static void do_free_init(struct work_struct *w);
+static DECLARE_WORK(init_free_wq, do_free_init);
+static LLIST_HEAD(init_free_list);
 
 #ifdef CONFIG_MODULES_TREE_LOOKUP
 
@@ -3551,14 +3552,6 @@ static void do_free_init(struct work_struct *w)
 	}
 }
 
-static int __init modules_wq_init(void)
-{
-	INIT_WORK(&init_free_wq, do_free_init);
-	init_llist_head(&init_free_list);
-	return 0;
-}
-module_init(modules_wq_init);
-
 /*
  * This is where the real work happens.
  *



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux