From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Pingfan Liu <kernelfans@gmail.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
James Morse <james.morse@arm.com>,
Matthias Brugger <mbrugger@suse.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>
Subject: Re: [PATCHv2] arm64: mm: Fix VM_BUG_ON(mm != &init_mm) for trans_pgd
Date: Tue, 16 Nov 2021 10:39:44 +0000 [thread overview]
Message-ID: <163705756834.1570573.6319251211753065459.b4-ty@kernel.org> (raw)
In-Reply-To: <20211112052214.9086-1-kernelfans@gmail.com>
On Fri, 12 Nov 2021 13:22:14 +0800, Pingfan Liu wrote:
> trans_pgd_create_copy() can hit "VM_BUG_ON(mm != &init_mm)" in the
> function pmd_populate_kernel().
>
> This is the combined consequence of commit 5de59884ac0e ("arm64:
> trans_pgd: pass NULL instead of init_mm to *_populate functions"), which
> replaced &init_mm with NULL and commit 59511cfd08f3 ("arm64: mm: use XN
> table mapping attributes for user/kernel mappings"), which introduced
> the VM_BUG_ON.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: mm: Fix VM_BUG_ON(mm != &init_mm) for trans_pgd
https://git.kernel.org/arm64/c/d3eb70ead647
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-11-16 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 6:03 [PATCH] arm64: mm: assign PXN permission in trans_pgd Pingfan Liu
2021-11-11 16:09 ` Catalin Marinas
2021-11-11 16:13 ` Ard Biesheuvel
2021-11-11 18:18 ` Catalin Marinas
2021-11-11 18:24 ` Catalin Marinas
2021-11-12 5:18 ` Pingfan Liu
2021-11-12 5:22 ` [PATCHv2] arm64: mm: Fix VM_BUG_ON(mm != &init_mm) for trans_pgd Pingfan Liu
2021-11-12 14:26 ` Catalin Marinas
2021-11-12 14:37 ` Pasha Tatashin
2021-11-16 10:39 ` Will Deacon [this message]
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=163705756834.1570573.6319251211753065459.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kernelfans@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mbrugger@suse.com \
--cc=pasha.tatashin@soleen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.