mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
To: Marco Elver <elver@google.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Alexander Potapenko <glider@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	kasan-dev <kasan-dev@googlegroups.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	<chinwen.chang@mediatek.com>, <nicholas.tang@mediatek.com>,
	<kuan-ying.lee@mediatek.com>
Subject: Re: [PATCH v3 0/3] kasan: add memory corruption identification support for hw tag-based kasan
Date: Sat, 26 Jun 2021 18:13:08 +0800	[thread overview]
Message-ID: <9e906af1182a9039886b0f86525106df381a6255.camel@mediatek.com> (raw)
In-Reply-To: <CANpmjNP9n8-m4MhY6Cdnfx_SYLVtG8NJ7raMUR+3rBoNyyfs+Q@mail.gmail.com>

On Mon, 2021-06-21 at 14:45 +0200, Marco Elver wrote:
> On Sun, 20 Jun 2021 at 13:48, Kuan-Ying Lee <
> Kuan-Ying.Lee@mediatek.com> wrote:
> > 
> > Add memory corruption identification for hardware tag-based KASAN
> > mode.
> > 
> > Changes since v3:
> >  - Preserve Copyright from hw_tags.c/sw_tags.c and
> >    report_sw_tags.c/report_hw_tags.c
> >  - Make non-trivial change in kasan sw tag-based mode
> > 
> > Changes since v2:
> >  - Thanks for Marco's Suggestion
> >  - Rename the CONFIG_KASAN_SW_TAGS_IDENTIFY
> >  - Integrate tag-based kasan common part
> >  - Rebase to latest linux-next
> > 
> > Kuan-Ying Lee (3):
> >   kasan: rename CONFIG_KASAN_SW_TAGS_IDENTIFY to
> >     CONFIG_KASAN_TAGS_IDENTIFY
> >   kasan: integrate the common part of two KASAN tag-based modes
> >   kasan: add memory corruption identification support for hardware
> >     tag-based mode
> 
> I think this looks fine, thank you for your efforts. How did you test
> this? Did you run the lib/test_kasan module with both SW_TAGS and
> HW_TAGS mode? I was about to run that before adding my Reviewed-by.

Thanks for the reminder.
Yes, I run the lib/test_kasan module with SW_TAGS and HW_TAGS mode. :)

> 
> Andrey, Alex, if you have time, please have a quick look at the
> series.
> 
> Thanks,
> -- Marco

      reply	other threads:[~2021-06-26 10:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20 11:47 Kuan-Ying Lee
2021-06-20 11:47 ` [PATCH v3 1/3] kasan: rename CONFIG_KASAN_SW_TAGS_IDENTIFY to CONFIG_KASAN_TAGS_IDENTIFY Kuan-Ying Lee
2021-06-22  9:28   ` Alexander Potapenko
2021-06-22 13:54   ` Andrey Konovalov
2021-06-20 11:47 ` [PATCH v3 2/3] kasan: integrate the common part of two KASAN tag-based modes Kuan-Ying Lee
2021-06-22  9:27   ` Alexander Potapenko
2021-06-22  9:48     ` Marco Elver
2021-06-22 13:54   ` Andrey Konovalov
2021-06-23  3:17     ` Kuan-Ying Lee
2021-06-20 11:47 ` [PATCH v3 3/3] kasan: add memory corruption identification support for hardware tag-based mode Kuan-Ying Lee
2021-06-22  9:29   ` Alexander Potapenko
2021-06-22 13:54   ` Andrey Konovalov
2021-06-23  4:12     ` Kuan-Ying Lee
2021-06-21 12:45 ` [PATCH v3 0/3] kasan: add memory corruption identification support for hw tag-based kasan Marco Elver
2021-06-26 10:13   ` Kuan-Ying Lee [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=9e906af1182a9039886b0f86525106df381a6255.camel@mediatek.com \
    --to=kuan-ying.lee@mediatek.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=chinwen.chang@mediatek.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nicholas.tang@mediatek.com \
    --cc=ryabinin.a.a@gmail.com \
    --cc=wsd_upstream@mediatek.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

all inboxes | Powered by JetHome®