Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Andrey Konovalov <andreyknvl@xxxxxxxxxx>, Dmitry Vyukov <dvyukov@xxxxxxxxxx>, Marco Elver <elver@xxxxxxxxxx>, Catalin Marinas <catalin.marinas@xxxxxxx>
Subject: Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
From: Vincenzo Frascino <vincenzo.frascino@xxxxxxx>
Date: Mon, 16 Nov 2020 14:50:17 +0000
Cc: Will Deacon <will.deacon@xxxxxxx>, Alexander Potapenko <glider@xxxxxxxxxx>, Evgenii Stepanov <eugenis@xxxxxxxxxx>, Kostya Serebryany <kcc@xxxxxxxxxx>, Peter Collingbourne <pcc@xxxxxxxxxx>, Serban Constantinescu <serbanc@xxxxxxxxxx>, Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>, Elena Petrova <lenaptr@xxxxxxxxxx>, Branislav Rankov <Branislav.Rankov@xxxxxxx>, Kevin Brodsky <kevin.brodsky@xxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, kasan-dev <kasan-dev@xxxxxxxxxxxxxxxx>, Linux ARM <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, Linux-MM <linux-mm@xxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <CAAeHK+xb4w1XSe_cXeV77d3VkHq6ABAKkKuEaFN-uFVY457-Ww@mail.gmail.com>
References: <cover.1603372719.git.andreyknvl@google.com> <ded454eeff88f631dc08eef76f0ad9f2daff0085.1603372719.git.andreyknvl@google.com> <CACT4Y+Zys3+VUsO6GDWQEcjCS6Wx16W_+B6aNy-fyhPcir7eeA@mail.gmail.com> <CAAeHK+xvGZNwTtvkzNnU7Hh7iUiPKFNDKDpKT8UPcqQk6Ah3yQ@mail.gmail.com> <CACT4Y+Z3UCwAY2Mm1KiQMBXVhc2Bobi-YrdiNYtToNgMRjOE4g@mail.gmail.com> <CANpmjNPNqHsOfcw7Wh+XQ_pPT1610-+B9By171t7KMS3aB2sBg@mail.gmail.com> <X7Jthb9D5Ekq93sS@trantor> <CACT4Y+ZubLBEiGZOVyptB4RPf=3Qr570GN+JBpSmaeEvHWQB5g@mail.gmail.com> <9d4156e6-ec4f-a742-a44e-f38bf7fa9ba9@arm.com> <CAAeHK+xb4w1XSe_cXeV77d3VkHq6ABAKkKuEaFN-uFVY457-Ww@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

On 11/16/20 1:50 PM, Andrey Konovalov wrote:
> Fixing this sounds like a good idea, but perhaps not as a part of this
> series, to not overinflate it even further.
> 
> I've filed a bug for this: https://bugzilla.kernel.org/show_bug.cgi?id=210221

Fine by me.

-- 
Regards,
Vincenzo

References:
- [PATCH RFC v2 00/21] kasan: hardware tag-based mode for production use on arm64
  - From: Andrey Konovalov
- [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Andrey Konovalov
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Dmitry Vyukov
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Andrey Konovalov
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Dmitry Vyukov
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Marco Elver
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Catalin Marinas
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Dmitry Vyukov
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Vincenzo Frascino
- Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
  - From: Andrey Konovalov

Prev by Date: x86 page_fault not succeeding when mapping write-only
Next by Date: Re: [PATCH 2/2] mm: memcg/slab: pre-allocate obj_cgroups for slab caches with SLAB_ACCOUNT
Previous by thread: Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK
Next by thread: [PATCH RFC v2 06/21] kasan: mark kasan_init_tags as __init
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]