mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shijie Huang <shijie@amperemail.onmicrosoft.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Huang Shijie <shijie@os.amperecomputing.com>,
	catalin.marinas@arm.com, will@kernel.org,
	anshuman.khandual@arm.com, corbet@lwn.net,
	patches@amperecomputing.com, cl@linux.com,
	akpm@linux-foundation.org, thuth@redhat.com, rostedt@goodmis.org,
	xiongwei.song@windriver.com, inux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2 fix] arm64: refactor the rodata=xxx
Date: Fri, 13 Dec 2024 16:46:31 +0800	[thread overview]
Message-ID: <56f10526-ea50-4d24-a042-d05b305e019e@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <CAMj1kXHXeiPiksuOabp-NXu0ORmmP1Jd1wZPmgAi09jsjaDAsQ@mail.gmail.com>


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


  reply	other threads:[~2024-12-13  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12  8:24 [PATCH v4 0/2] " Huang Shijie
2024-12-12  8:24 ` [PATCH v4 1/2] " Huang Shijie
2024-12-13  5:30   ` [PATCH v4 1/2 fix] " Huang Shijie
2024-12-13  7:30     ` Ard Biesheuvel
2024-12-13  8:22       ` Shijie Huang
2024-12-13  8:26         ` Ard Biesheuvel
2024-12-13  8:46           ` Shijie Huang [this message]
2024-12-17  7:17   ` [PATCH v4 1/2 fix-v2 ] " Huang Shijie
2025-06-27 15:44     ` Will Deacon
2025-06-30  1:40       ` Shijie Huang
2024-12-12  8:24 ` [PATCH v4 2/2] arm64/Kconfig: Remove CONFIG_RODATA_FULL_DEFAULT_ENABLED Huang Shijie

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=56f10526-ea50-4d24-a042-d05b305e019e@amperemail.onmicrosoft.com \
    --to=shijie@amperemail.onmicrosoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=cl@linux.com \
    --cc=corbet@lwn.net \
    --cc=inux-doc@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@amperecomputing.com \
    --cc=rostedt@goodmis.org \
    --cc=shijie@os.amperecomputing.com \
    --cc=thuth@redhat.com \
    --cc=will@kernel.org \
    --cc=xiongwei.song@windriver.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®