From: Enlin Mu <enlin.mu@outlook.com>
To: catalin.marinas@arm.com, will@kernel.org, enlin.mu@unisoc.com,
enlinmu@gmail.com, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] arm64: remove kaslr-seed node when it had used
Date: Tue, 14 Nov 2023 21:55:51 +0800 [thread overview]
Message-ID: <TYSPR04MB7084AFDB414AA7AE49A02D608AB2A@TYSPR04MB7084.apcprd04.prod.outlook.com> (raw)
From: Enlin Mu <enlin.mu@unisoc.com>
If this node value is zero,it means that kaslr is enabled.
Removing it for the system safe,nobody knows if this feature is
enable or not.
Signed-off-by: Enlin Mu <enlin.mu@unisoc.com>
---
arch/arm64/kernel/pi/kaslr_early.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/pi/kaslr_early.c b/arch/arm64/kernel/pi/kaslr_early.c
index 17bff6e399e4..bc35d4ed84b7 100644
--- a/arch/arm64/kernel/pi/kaslr_early.c
+++ b/arch/arm64/kernel/pi/kaslr_early.c
@@ -81,7 +81,7 @@ static u64 get_kaslr_seed(void *fdt)
return 0;
ret = fdt64_to_cpu(*prop);
- *prop = 0;
+ fdt_nop_property(fdt, node, "kaslr-seed");
return ret;
}
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Enlin Mu <enlin.mu@outlook.com>
To: catalin.marinas@arm.com, will@kernel.org, enlin.mu@unisoc.com,
enlinmu@gmail.com, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] arm64: remove kaslr-seed node when it had used
Date: Tue, 14 Nov 2023 21:55:51 +0800 [thread overview]
Message-ID: <TYSPR04MB7084AFDB414AA7AE49A02D608AB2A@TYSPR04MB7084.apcprd04.prod.outlook.com> (raw)
From: Enlin Mu <enlin.mu@unisoc.com>
If this node value is zero,it means that kaslr is enabled.
Removing it for the system safe,nobody knows if this feature is
enable or not.
Signed-off-by: Enlin Mu <enlin.mu@unisoc.com>
---
arch/arm64/kernel/pi/kaslr_early.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/pi/kaslr_early.c b/arch/arm64/kernel/pi/kaslr_early.c
index 17bff6e399e4..bc35d4ed84b7 100644
--- a/arch/arm64/kernel/pi/kaslr_early.c
+++ b/arch/arm64/kernel/pi/kaslr_early.c
@@ -81,7 +81,7 @@ static u64 get_kaslr_seed(void *fdt)
return 0;
ret = fdt64_to_cpu(*prop);
- *prop = 0;
+ fdt_nop_property(fdt, node, "kaslr-seed");
return ret;
}
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-11-14 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 13:55 Enlin Mu [this message]
2023-11-14 13:55 ` [PATCH] arm64: remove kaslr-seed node when it had used Enlin Mu
2023-11-17 11:29 ` Will Deacon
2023-11-17 11:29 ` Will Deacon
2023-11-17 15:02 ` kernel test robot
2023-11-17 15:02 ` kernel test robot
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=TYSPR04MB7084AFDB414AA7AE49A02D608AB2A@TYSPR04MB7084.apcprd04.prod.outlook.com \
--to=enlin.mu@outlook.com \
--cc=catalin.marinas@arm.com \
--cc=enlin.mu@unisoc.com \
--cc=enlinmu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.