Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Catalin Marinas <catalin.marinas@arm.com>
To:     will@kernel.org, Dan Li <ashimida@linux.alibaba.com>
Cc:     linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC]arm64:Mark __stack_chk_guard as __ro_after_init
Date:   Thu, 16 Sep 2021 18:08:25 +0100
Message-Id: <163181210192.884883.7181525441852917097.b4-ty@arm.com>
In-Reply-To: <1631612642-102881-1-git-send-email-ashimida@linux.alibaba.com>
References: <1631612642-102881-1-git-send-email-ashimida@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 14 Sep 2021 17:44:02 +0800, Dan Li wrote:
> __stack_chk_guard is setup once while init stage and never changed
> after that.
> 
> Although the modification of this variable at runtime will usually
> cause the kernel to crash (so dose the attacker), it should be marked
> as _ro_after_init, and it should not affect performance if it is
> placed in the ro_after_init section.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64:Mark __stack_chk_guard as __ro_after_init
      https://git.kernel.org/arm64/c/9fcb2e93f41c

-- 
Catalin