linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peter Collingbourne <pcc@google.com>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Mark Brown <broonie@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Andrey Konovalov <andreyknvl@google.com>,
	 Evgenii Stepanov <eugenis@google.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/3] kasan: arm64: support specialized outlined tag mismatch checks
Date: Wed, 12 May 2021 19:30:35 -0700	[thread overview]
Message-ID: <CAMn1gO6QyTtUZDzx2AJsW-no8K2No2iRUmXpvjCJQGRYVyij4Q@mail.gmail.com> (raw)
In-Reply-To: <20210120124109.GB19504@willie-the-truck>

On Wed, Jan 20, 2021 at 4:41 AM Will Deacon <will@kernel.org> wrote:
>
> On Tue, Dec 08, 2020 at 05:49:07PM +0000, Catalin Marinas wrote:
> > On Wed, Dec 02, 2020 at 09:12:24PM -0800, Peter Collingbourne wrote:
> > > By using outlined checks we can achieve a significant code size
> > > improvement by moving the tag-based ASAN checks into separate
> > > functions. Unlike the existing CONFIG_KASAN_OUTLINE mode these
> > > functions have a custom calling convention that preserves most
> > > registers and is specialized to the register containing the address
> > > and the type of access, and as a result we can eliminate the code
> > > size and performance overhead of a standard calling convention such
> > > as AAPCS for these functions.
>
> [...]
>
> > >  arch/arm64/include/asm/asm-prototypes.h |  6 ++
> > >  arch/arm64/include/asm/module.lds.h     | 17 +++++-
> > >  arch/arm64/lib/Makefile                 |  2 +
> > >  arch/arm64/lib/kasan_sw_tags.S          | 76 +++++++++++++++++++++++++
> > >  mm/kasan/tags.c                         |  7 +++
> > >  scripts/Makefile.kasan                  |  1 +
> >
> > I can try to queue the series but this patch would need an ack on the
> > kasan changes.
> >
> > (also, it may conflict with linux-next which renames tags.c to sw_tags.c
> > but that's trivial)
>
> Looks like this didn't land for 5.11. Peter -- please can you send a rebased
> version (on -rc4) so that I can queue it for 5.12?

Sorry for dropping the ball on this -- I've sent out a rebased v4 that
should be ready to go into 5.14 -- I guess it's too late for 5.13.

Peter

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-05-13  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  5:12 [PATCH v3 1/3] arm64: Change the on_*stack functions to take a size argument Peter Collingbourne
2020-12-03  5:12 ` [PATCH v3 2/3] arm64: stacktrace: Relax frame record alignment requirement to 8 bytes Peter Collingbourne
2020-12-03  5:12 ` [PATCH v3 3/3] kasan: arm64: support specialized outlined tag mismatch checks Peter Collingbourne
2020-12-08 17:49   ` Catalin Marinas
2021-01-20 12:41     ` Will Deacon
2021-05-13  2:30       ` Peter Collingbourne [this message]
2021-01-07 15:20   ` Andrey Konovalov
2020-12-08 10:20 ` [PATCH v3 1/3] arm64: Change the on_*stack functions to take a size argument Mark Rutland

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=CAMn1gO6QyTtUZDzx2AJsW-no8K2No2iRUmXpvjCJQGRYVyij4Q@mail.gmail.com \
    --to=pcc@google.com \
    --cc=andreyknvl@google.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=eugenis@google.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).