[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0315df9-b122-46cd-12b2-7704d4a4392e@gentwo.org>
Date: Fri, 5 Jul 2024 10:05:29 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Catalin Marinas <catalin.marinas@....com>
cc: Yang Shi <yang@...amperecomputing.com>, will@...nel.org,
anshuman.khandual@....com, david@...hat.com, scott@...amperecomputing.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [v5 PATCH] arm64: mm: force write fault for atomic RMW
instructions
On Thu, 4 Jul 2024, Catalin Marinas wrote:
> It could be worked around with a new flavour of get_user() that uses the
> non-T LDR instruction and the user mapping is readable by the kernel
> (that's the case with EPAN, prior to PIE and I think we can change this
> for PIE configurations as well). But it adds to the complexity of this
> patch when the kernel already offers a MADV_POPULATE_WRITE solution.
The use of MADV_POPULATE_WRITE here is arch specific and not a general
solution. It requires specialized knowledge and research before someone
can figure out that this particular trick is required on Linux ARM64
processors. The builders need to detect this special situation in the
build process and activate this workaround.
It would be much simpler to just merge the patch and be done with it.
Otherwise this issue will continue to cause uncountably many hours of
anguish for sysadmins and developers all over the Linux ecosystem trying
to figure out what in the world is going on with ARM.
Powered by blists - more mailing lists