[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200508123132.830428928@linuxfoundation.org>
Date: Fri, 8 May 2020 14:31:50 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org, Rene Herman <rene.herman@...access.nl>,
William Breathitt Gray <vilhelm.gray@...il.com>
Subject: [PATCH 4.4 119/312] isa: Call isa_bus_init before dependent ISA bus drivers register
From: William Breathitt Gray <vilhelm.gray@...il.com>
commit 32a5a0c047343b11f581f663a2309cf43d13466f upstream.
The isa_bus_init function must be called before drivers which utilize
the ISA bus driver are registered. A race condition for initilization
exists if device_initcall is used (the isa_bus_init callback is placed
in the same initcall level as dependent drivers which use module_init).
This patch ensures that isa_bus_init is called first by utilizing
postcore_initcall in favor of device_initcall.
Fixes: a5117ba7da37 ("[PATCH] Driver model: add ISA bus")
Cc: Rene Herman <rene.herman@...access.nl>
Signed-off-by: William Breathitt Gray <vilhelm.gray@...il.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
drivers/base/isa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/base/isa.c
+++ b/drivers/base/isa.c
@@ -180,4 +180,4 @@ static int __init isa_bus_init(void)
return error;
}
-device_initcall(isa_bus_init);
+postcore_initcall(isa_bus_init);
Powered by blists - more mailing lists