From: Robin Murphy <robin.murphy@arm.com>
To: Will Deacon <will@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH V2] arm64/mm: Intercept pfn changes in set_pte_at()
Date: Fri, 27 Jan 2023 12:43:17 +0000 [thread overview]
Message-ID: <d454c9a2-5300-b600-a2ae-21d82d338470@arm.com> (raw)
In-Reply-To: <20230126133321.GB29148@willie-the-truck>
On 2023-01-26 13:33, Will Deacon wrote:
> On Tue, Jan 24, 2023 at 11:11:49AM +0530, Anshuman Khandual wrote:
>> On 1/9/23 10:58, Anshuman Khandual wrote:
>>> Changing pfn on a user page table mapped entry, without first going through
>>> break-before-make (BBM) procedure is unsafe. This just updates set_pte_at()
>>> to intercept such changes, via an updated pgattr_change_is_safe(). This new
>>> check happens via __check_racy_pte_update(), which has now been renamed as
>>> __check_safe_pte_update().
>>>
>>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>>> Cc: Will Deacon <will@kernel.org>
>>> Cc: Mark Rutland <mark.rutland@arm.com>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> Cc: linux-arm-kernel@lists.infradead.org
>>> Cc: linux-kernel@vger.kernel.org
>>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>>> ---
>>> This applies on v6.2-rc3. This patch had some test time on an internal CI
>>> system without any issues being reported.
>>
>> Gentle ping, any updates on this patch ? Still any concerns ?
>
> I don't think we really got to the bottom of Mark's concerns with
> unreachable ptes on the stack, did we? I also have vague recollections
> of somebody (Robin?) running into issues with the vmap code not honouring
> BBM.
Doesn't ring a bell, so either it wasn't me, or it was many years ago
and about 5 levels deep into trying to fix something else :/
> So I think we should confirm/fix the vmap issue before we enable this check
> and also try to get some testing coverage to address Mark's worries. I think
> he has a syzkaller instance set up, so that sound like a good place to
> start.
I think we're also missing a subtlety here in that this restriction
doesn't *always* apply. For instance if someone wants to move a page by
making the mapping read-only, copying the contents to a new page, then
pointing the RO mapping at that new page, that should technically not
require BBM.
Thanks,
Robin.
next prev parent reply other threads:[~2023-01-27 12:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 5:28 Anshuman Khandual
2023-01-24 5:41 ` Anshuman Khandual
2023-01-26 13:33 ` Will Deacon
2023-01-27 12:43 ` Robin Murphy [this message]
2023-01-31 15:49 ` Will Deacon
2023-02-01 12:20 ` Catalin Marinas
2023-02-02 9:51 ` Muchun Song
2023-02-02 10:45 ` Catalin Marinas
2023-02-03 2:40 ` Muchun Song
2023-02-03 10:10 ` Will Deacon
2023-02-06 3:28 ` Muchun Song
2023-02-07 14:31 ` Will Deacon
2023-02-08 3:13 ` Muchun Song
2023-02-08 17:27 ` Mark Rutland
2023-02-10 6:50 ` Muchun Song
2023-01-27 15:16 ` Mark Rutland
2023-01-30 8:16 ` Anshuman Khandual
2023-01-30 10:08 ` Mark Rutland
2023-01-27 15:14 ` Mark Rutland
2023-01-31 2:57 ` Anshuman Khandual
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=d454c9a2-5300-b600-a2ae-21d82d338470@arm.com \
--to=robin.murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 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®