From: Catalin Marinas <catalin.marinas@arm.com>
To: Derrick McKee <derrick.mckee@gmail.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Removed MTE function
Date: Mon, 26 Apr 2021 18:07:46 +0100 [thread overview]
Message-ID: <20210426170746.GH4985@arm.com> (raw)
In-Reply-To: <CAJoBWHwvkoTx=01FQDn6TcsFUPps_7cmjLG3nopJMdpHOJEvhw@mail.gmail.com>
On Fri, Apr 16, 2021 at 01:58:27PM -0400, Derrick McKee wrote:
> On Fri, Apr 2, 2021 at 8:34 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > It was added in commit 85f49cae4dfc ("arm64: mte: add in-kernel MTE
> > helpers") in 5.11 but moved out of mte.S by commit 2cb34276427a ("arm64:
> > kasan: simplify and inline MTE functions") in 5.12 and renamed to
> > mte_set_mem_tag_range(). Unfortunately, that commit did not delete the
> > old function prototypes in mte.h. I'll clean it up next week, unless
> > someone beats me to it with a patch.
>
> Ahh, ok, thanks for the information.
>
> > What do you need this function for? It's supposed to be used only by
> > kasan, hence moved to mte-kasan.h.
>
> I am working on a research prototype attempting to harden kernel
> modules using a combination of MTE and PAC. I'd actually be
> interested in hearing how KASAN handles dynamic percpu allocations,
> because that's been a challenge for me in this project.
At a quick look, I don't think it does anything special. It relies on
the page allocator to set a tag on the page and I presume it uses that
tag. However, individual objects won't be tagged differently, nor the
tag reset on free.
--
Catalin
_______________________________________________
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-04-26 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 11:26 Removed MTE function Derrick McKee
2021-04-02 12:34 ` Catalin Marinas
2021-04-16 17:58 ` Derrick McKee
2021-04-26 17:07 ` Catalin Marinas [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=20210426170746.GH4985@arm.com \
--to=catalin.marinas@arm.com \
--cc=andreyknvl@gmail.com \
--cc=derrick.mckee@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vincenzo.frascino@arm.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.