[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170614191152.28089.65392.stgit@tlendack-t1.amdoffice.net>
Date: Wed, 14 Jun 2017 14:11:52 -0500
From: Tom Lendacky <thomas.lendacky@....com>
To: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Cc: Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...e.de>,
Ingo Molnar <mingo@...nel.org>
Subject: [PATCH tip/sched/core] mm/early_ioremap: Adjust early_ioremap
system_state check
A recent change added a new system_state value, SYSTEM_SCHEDULING, which
exposed a warning issued by early_ioreamp() when the system_state was not
SYSTEM_BOOTING. Since early_ioremap() can be called when the system_state
is SYSTEM_SCHEDULING, the check to issue the warning is changed from
system_state != SYSTEM_BOOTING to system_state >= SYSTEM_RUNNING.
Signed-off-by: Tom Lendacky <thomas.lendacky@....com>
---
mm/early_ioremap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/early_ioremap.c b/mm/early_ioremap.c
index 6d5717b..57540de 100644
--- a/mm/early_ioremap.c
+++ b/mm/early_ioremap.c
@@ -103,7 +103,7 @@ static int __init check_early_ioremap_leak(void)
enum fixed_addresses idx;
int i, slot;
- WARN_ON(system_state != SYSTEM_BOOTING);
+ WARN_ON(system_state >= SYSTEM_RUNNING);
slot = -1;
for (i = 0; i < FIX_BTMAPS_SLOTS; i++) {
Powered by blists - more mailing lists