From: Thomas Gleixner <tglx@linutronix.de>
To: Ard Biesheuvel <ardb@kernel.org>, linux-mm@kvack.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
Quanyang Wang <quanyang.wang@windriver.com>,
Linus Walleij <linus.walleij@linaro.org>,
Russell King <linux@armlinux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH resend] kmap_local: don't assume kmap PTEs are linear arrays in memory
Date: Thu, 25 Nov 2021 12:00:56 +0100 [thread overview]
Message-ID: <875ysgmrdj.ffs@tglx> (raw)
In-Reply-To: <20211116094737.7391-1-ardb@kernel.org>
On Tue, Nov 16 2021 at 10:47, Ard Biesheuvel wrote:
> The kmap_local conversion broke the ARM architecture, because the new
> code assumes that all PTEs used for creating kmaps form a linear array
> in memory, and uses array indexing to look up the kmap PTE belonging to
> a certain kmap index.
>
> On ARM, this cannot work, not only because the PTE pages may be
> non-adjacent in memory, but also because ARM/!LPAE interleaves hardware
> entries and extended entries (carrying software-only bits) in a way that
> is not compatible with array indexing.
>
> Fortunately, this only seems to affect configurations with more than 8
> CPUs, due to the way the per-CPU kmap slots are organized in memory.
Ooops. I completely missed that detail. Sorry for the wreckage.
> Work around this by permitting an architecture to set a Kconfig symbol
> that signifies that the kmap PTEs do not form a lineary array in memory,
> and so the only way to locate the appropriate one is to walk the page
> tables.
> +static pte_t *kmap_get_pte(unsigned long vaddr, int idx)
> {
> + if (IS_ENABLED(CONFIG_KMAP_LOCAL_NON_LINEAR_PTE_ARRAY))
> + /*
> + * Set by the arch if __kmap_pte[-idx] does not produce
> + * the correct entry.
> + */
> + return virt_to_kpte(vaddr);
Nit. The above is not a one line statement (even if it is from a
compiler perspective).
/*
* Does the architecture have non-linear KMAP pte entries which
* cannot be accessed by index?
*/
if (IS_ENABLED(CONFIG_KMAP_LOCAL_NON_LINEAR_PTE_ARRAY))
return virt_to_kpte(vaddr);
or
if (IS_ENABLED(CONFIG_KMAP_LOCAL_NON_LINEAR_PTE_ARRAY)) {
/* PTE entries cannot be accessed by index. */
return virt_to_kpte(vaddr);
}
are readable but this is really breaking the brain OCR:
if (IS_ENABLED(CONFIG_KMAP_LOCAL_NON_LINEAR_PTE_ARRAY))
/*
* Set by the arch if __kmap_pte[-idx] does not produce
* the correct entry.
*/
return virt_to_kpte(vaddr);
if (!__kmap_pte)
Other than that.
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
prev parent reply other threads:[~2021-11-25 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 9:47 [PATCH resend] kmap_local: don't assume kmap PTEs are linear arrays in memory Ard Biesheuvel
2021-11-16 12:04 ` Russell King (Oracle)
2021-11-16 22:12 ` Andrew Morton
2021-11-16 22:13 ` Ard Biesheuvel
2021-11-16 22:15 ` Ard Biesheuvel
2021-11-25 11:00 ` Thomas Gleixner [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=875ysgmrdj.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=quanyang.wang@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;
as well as URLs for NNTP newsgroup(s).