[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56f10526-ea50-4d24-a042-d05b305e019e@amperemail.onmicrosoft.com>
Date: Fri, 13 Dec 2024 16:46:31 +0800
From: Shijie Huang <shijie@...eremail.onmicrosoft.com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Huang Shijie <shijie@...amperecomputing.com>, catalin.marinas@....com,
will@...nel.org, anshuman.khandual@....com, corbet@....net,
patches@...erecomputing.com, cl@...ux.com, akpm@...ux-foundation.org,
thuth@...hat.com, rostedt@...dmis.org, xiongwei.song@...driver.com,
inux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 1/2 fix] arm64: refactor the rodata=xxx
On 2024/12/13 16:26, Ard Biesheuvel wrote:
>>> How do you envisage 'noalias' becoming a security feature? The point
>> for the case 2) above, if its linear alias is also mapped as read-only,
>>
>> can we think it is safe as the original "rodata=full"?
>>
> No, it is not. Why would we bother with rodata=full (which is costly
> in terms of TLB pressure) if rodata=noalias is equally safe?
okay, thanks.
I will wait for two days, and send out the new patch if there no other
comment.
Thanks
Huang Shijie
Powered by blists - more mailing lists