From: Andrey Konovalov <andreyknvl@google.com> To: Dmitry Vyukov <dvyukov@google.com>, Alexander Potapenko <glider@google.com>, Marco Elver <elver@google.com> Cc: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Vincenzo Frascino <vincenzo.frascino@arm.com>, Evgenii Stepanov <eugenis@google.com>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Branislav Rankov <Branislav.Rankov@arm.com>, Kevin Brodsky <kevin.brodsky@arm.com>, Andrew Morton <akpm@linux-foundation.org>, kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrey Konovalov <andreyknvl@google.com> Subject: [PATCH v2 00/20] kasan: boot parameters for hardware tag-based mode Date: Tue, 10 Nov 2020 23:20:04 +0100 [thread overview] Message-ID: <cover.1605046662.git.andreyknvl@google.com> (raw) === Overview Hardware tag-based KASAN mode [1] is intended to eventually be used in production as a security mitigation. Therefore there's a need for finer control over KASAN features and for an existence of a kill switch. This patchset adds a few boot parameters for hardware tag-based KASAN that allow to disable or otherwise control particular KASAN features, as well as provides some initial optimizations for running KASAN in production. There's another planned patchset what will further optimize hardware tag-based KASAN, provide proper benchmarking and tests, and will fully enable tag-based KASAN for production use. Hardware tag-based KASAN relies on arm64 Memory Tagging Extension (MTE) [2] to perform memory and pointer tagging. Please see [3] and [4] for detailed analysis of how MTE helps to fight memory safety problems. The features that can be controlled are: 1. Whether KASAN is enabled at all. 2. Whether KASAN collects and saves alloc/free stacks. 3. Whether KASAN panics on a detected bug or not. The patch titled "kasan: add and integrate kasan boot parameters" of this series adds a few new boot parameters. kasan.mode allows to choose one of three main modes: - kasan.mode=off - KASAN is disabled, no tag checks are performed - kasan.mode=prod - only essential production features are enabled - kasan.mode=full - all KASAN features are enabled The chosen mode provides default control values for the features mentioned above. However it's also possible to override the default values by providing: - kasan.stacktrace=off/on - enable stacks collection (default: on for mode=full, otherwise off) - kasan.fault=report/panic - only report tag fault or also panic (default: report) If kasan.mode parameter is not provided, it defaults to full when CONFIG_DEBUG_KERNEL is enabled, and to prod otherwise. It is essential that switching between these modes doesn't require rebuilding the kernel with different configs, as this is required by the Android GKI (Generic Kernel Image) initiative. === Benchmarks For now I've only performed a few simple benchmarks such as measuring kernel boot time and slab memory usage after boot. There's an upcoming patchset which will optimize KASAN further and include more detailed benchmarking results. The benchmarks were performed in QEMU and the results below exclude the slowdown caused by QEMU memory tagging emulation (as it's different from the slowdown that will be introduced by hardware and is therefore irrelevant). KASAN_HW_TAGS=y + kasan.mode=off introduces no performance or memory impact compared to KASAN_HW_TAGS=n. kasan.mode=prod (manually excluding tagging) introduces 3% of performance and no memory impact (except memory used by hardware to store tags) compared to kasan.mode=off. kasan.mode=full has about 40% performance and 30% memory impact over kasan.mode=prod. Both come from alloc/free stack collection. === Notes This patchset is available here: https://github.com/xairy/linux/tree/up-boot-mte-v2 and on Gerrit here: https://linux-review.googlesource.com/c/linux/kernel/git/torvalds/linux/+/3707 This patchset is based on v9 of "kasan: add hardware tag-based mode for arm64" patchset [1]. For testing in QEMU hardware tag-based KASAN requires: 1. QEMU built from master [6] (use "-machine virt,mte=on -cpu max" arguments to run). 2. GCC version 10. [1] https://lkml.org/lkml/2020/11/10/1187 [2] https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/enhancing-memory-safety [3] https://arxiv.org/pdf/1802.09517.pdf [4] https://github.com/microsoft/MSRC-Security-Research/blob/master/papers/2020/Security%20analysis%20of%20memory%20tagging.pdf [5] https://source.android.com/devices/architecture/kernel/generic-kernel-image [6] https://github.com/qemu/qemu === History Changes v1 -> v2: - Rebased onto v9 of the HW_TAGS patchset. - Don't initialize static branches in kasan_init_hw_tags_cpu(), as cpu_enable_mte() can't sleep; do in in kasan_init_hw_tags() instead. - Rename kasan.stacks to kasan.stacktrace. Changes RFC v2 -> v1: - Rebrand the patchset from fully enabling production use to partially addressing that; another optimization and testing patchset will be required. - Rebase onto v8 of KASAN_HW_TAGS series. - Fix "ASYNC" -> "async" typo. - Rework depends condition for VMAP_STACK and update config text. - Remove unneeded reset_tag() macro, use kasan_reset_tag() instead. - Rename kasan.stack to kasan.stacks to avoid confusion with stack instrumentation. - Introduce kasan_stack_collection_enabled() and kasan_is_enabled() helpers. - Simplify kasan_stack_collection_enabled() usage. - Rework SLAB_KASAN flag and metadata allocation (see the corresponding patch for details). - Allow cache merging with KASAN_HW_TAGS when kasan.stacks is off. - Use sync mode dy default for both prod and full KASAN modes. - Drop kasan.trap=sync/async boot parameter, as async mode isn't supported yet. - Choose prod or full mode depending on CONFIG_DEBUG_KERNEL when no kasan.mode boot parameter is provided. - Drop krealloc optimization changes, those will be included in a separate patchset. - Update KASAN documentation to mention boot parameters. Changes RFC v1 -> RFC v2: - Rework boot parameters. - Drop __init from empty kasan_init_tags() definition. - Add cpu_supports_mte() helper that can be used during early boot and use it in kasan_init_tags() - Lots of new KASAN optimization commits. Andrey Konovalov (20): kasan: simplify quarantine_put call site kasan: rename get_alloc/free_info kasan: introduce set_alloc_info kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK kasan: allow VMAP_STACK for HW_TAGS mode kasan: remove __kasan_unpoison_stack kasan: inline kasan_reset_tag for tag-based modes kasan: inline random_tag for HW_TAGS kasan: inline kasan_poison_memory and check_invalid_free kasan: inline and rename kasan_unpoison_memory kasan: add and integrate kasan boot parameters kasan, mm: check kasan_enabled in annotations kasan: simplify kasan_poison_kfree kasan, mm: rename kasan_poison_kfree kasan: don't round_up too much kasan: simplify assign_tag and set_tag calls kasan: clarify comment in __kasan_kfree_large kasan: clean up metadata allocation and usage kasan, mm: allow cache merging with no metadata kasan: update documentation Documentation/dev-tools/kasan.rst | 180 ++++++++++++-------- arch/Kconfig | 8 +- arch/arm64/kernel/sleep.S | 2 +- arch/x86/kernel/acpi/wakeup_64.S | 2 +- include/linux/kasan.h | 253 +++++++++++++++++++++------ include/linux/mm.h | 22 ++- kernel/fork.c | 2 +- mm/kasan/common.c | 274 ++++++++++++++++++------------ mm/kasan/generic.c | 27 +-- mm/kasan/hw_tags.c | 183 ++++++++++++++++---- mm/kasan/kasan.h | 113 ++++++++---- mm/kasan/quarantine.c | 13 +- mm/kasan/report.c | 61 ++++--- mm/kasan/report_hw_tags.c | 2 +- mm/kasan/report_sw_tags.c | 13 +- mm/kasan/shadow.c | 5 +- mm/kasan/sw_tags.c | 17 +- mm/mempool.c | 2 +- mm/slab_common.c | 13 +- 19 files changed, 826 insertions(+), 366 deletions(-) -- 2.29.2.222.g5d2a92d10f8-goog
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Konovalov <andreyknvl@google.com> To: Dmitry Vyukov <dvyukov@google.com>, Alexander Potapenko <glider@google.com>, Marco Elver <elver@google.com> Cc: Branislav Rankov <Branislav.Rankov@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, Kevin Brodsky <kevin.brodsky@arm.com>, Will Deacon <will.deacon@arm.com>, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, Andrey Konovalov <andreyknvl@google.com>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Andrew Morton <akpm@linux-foundation.org>, Vincenzo Frascino <vincenzo.frascino@arm.com>, Evgenii Stepanov <eugenis@google.com> Subject: [PATCH v2 00/20] kasan: boot parameters for hardware tag-based mode Date: Tue, 10 Nov 2020 23:20:04 +0100 [thread overview] Message-ID: <cover.1605046662.git.andreyknvl@google.com> (raw) === Overview Hardware tag-based KASAN mode [1] is intended to eventually be used in production as a security mitigation. Therefore there's a need for finer control over KASAN features and for an existence of a kill switch. This patchset adds a few boot parameters for hardware tag-based KASAN that allow to disable or otherwise control particular KASAN features, as well as provides some initial optimizations for running KASAN in production. There's another planned patchset what will further optimize hardware tag-based KASAN, provide proper benchmarking and tests, and will fully enable tag-based KASAN for production use. Hardware tag-based KASAN relies on arm64 Memory Tagging Extension (MTE) [2] to perform memory and pointer tagging. Please see [3] and [4] for detailed analysis of how MTE helps to fight memory safety problems. The features that can be controlled are: 1. Whether KASAN is enabled at all. 2. Whether KASAN collects and saves alloc/free stacks. 3. Whether KASAN panics on a detected bug or not. The patch titled "kasan: add and integrate kasan boot parameters" of this series adds a few new boot parameters. kasan.mode allows to choose one of three main modes: - kasan.mode=off - KASAN is disabled, no tag checks are performed - kasan.mode=prod - only essential production features are enabled - kasan.mode=full - all KASAN features are enabled The chosen mode provides default control values for the features mentioned above. However it's also possible to override the default values by providing: - kasan.stacktrace=off/on - enable stacks collection (default: on for mode=full, otherwise off) - kasan.fault=report/panic - only report tag fault or also panic (default: report) If kasan.mode parameter is not provided, it defaults to full when CONFIG_DEBUG_KERNEL is enabled, and to prod otherwise. It is essential that switching between these modes doesn't require rebuilding the kernel with different configs, as this is required by the Android GKI (Generic Kernel Image) initiative. === Benchmarks For now I've only performed a few simple benchmarks such as measuring kernel boot time and slab memory usage after boot. There's an upcoming patchset which will optimize KASAN further and include more detailed benchmarking results. The benchmarks were performed in QEMU and the results below exclude the slowdown caused by QEMU memory tagging emulation (as it's different from the slowdown that will be introduced by hardware and is therefore irrelevant). KASAN_HW_TAGS=y + kasan.mode=off introduces no performance or memory impact compared to KASAN_HW_TAGS=n. kasan.mode=prod (manually excluding tagging) introduces 3% of performance and no memory impact (except memory used by hardware to store tags) compared to kasan.mode=off. kasan.mode=full has about 40% performance and 30% memory impact over kasan.mode=prod. Both come from alloc/free stack collection. === Notes This patchset is available here: https://github.com/xairy/linux/tree/up-boot-mte-v2 and on Gerrit here: https://linux-review.googlesource.com/c/linux/kernel/git/torvalds/linux/+/3707 This patchset is based on v9 of "kasan: add hardware tag-based mode for arm64" patchset [1]. For testing in QEMU hardware tag-based KASAN requires: 1. QEMU built from master [6] (use "-machine virt,mte=on -cpu max" arguments to run). 2. GCC version 10. [1] https://lkml.org/lkml/2020/11/10/1187 [2] https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/enhancing-memory-safety [3] https://arxiv.org/pdf/1802.09517.pdf [4] https://github.com/microsoft/MSRC-Security-Research/blob/master/papers/2020/Security%20analysis%20of%20memory%20tagging.pdf [5] https://source.android.com/devices/architecture/kernel/generic-kernel-image [6] https://github.com/qemu/qemu === History Changes v1 -> v2: - Rebased onto v9 of the HW_TAGS patchset. - Don't initialize static branches in kasan_init_hw_tags_cpu(), as cpu_enable_mte() can't sleep; do in in kasan_init_hw_tags() instead. - Rename kasan.stacks to kasan.stacktrace. Changes RFC v2 -> v1: - Rebrand the patchset from fully enabling production use to partially addressing that; another optimization and testing patchset will be required. - Rebase onto v8 of KASAN_HW_TAGS series. - Fix "ASYNC" -> "async" typo. - Rework depends condition for VMAP_STACK and update config text. - Remove unneeded reset_tag() macro, use kasan_reset_tag() instead. - Rename kasan.stack to kasan.stacks to avoid confusion with stack instrumentation. - Introduce kasan_stack_collection_enabled() and kasan_is_enabled() helpers. - Simplify kasan_stack_collection_enabled() usage. - Rework SLAB_KASAN flag and metadata allocation (see the corresponding patch for details). - Allow cache merging with KASAN_HW_TAGS when kasan.stacks is off. - Use sync mode dy default for both prod and full KASAN modes. - Drop kasan.trap=sync/async boot parameter, as async mode isn't supported yet. - Choose prod or full mode depending on CONFIG_DEBUG_KERNEL when no kasan.mode boot parameter is provided. - Drop krealloc optimization changes, those will be included in a separate patchset. - Update KASAN documentation to mention boot parameters. Changes RFC v1 -> RFC v2: - Rework boot parameters. - Drop __init from empty kasan_init_tags() definition. - Add cpu_supports_mte() helper that can be used during early boot and use it in kasan_init_tags() - Lots of new KASAN optimization commits. Andrey Konovalov (20): kasan: simplify quarantine_put call site kasan: rename get_alloc/free_info kasan: introduce set_alloc_info kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK kasan: allow VMAP_STACK for HW_TAGS mode kasan: remove __kasan_unpoison_stack kasan: inline kasan_reset_tag for tag-based modes kasan: inline random_tag for HW_TAGS kasan: inline kasan_poison_memory and check_invalid_free kasan: inline and rename kasan_unpoison_memory kasan: add and integrate kasan boot parameters kasan, mm: check kasan_enabled in annotations kasan: simplify kasan_poison_kfree kasan, mm: rename kasan_poison_kfree kasan: don't round_up too much kasan: simplify assign_tag and set_tag calls kasan: clarify comment in __kasan_kfree_large kasan: clean up metadata allocation and usage kasan, mm: allow cache merging with no metadata kasan: update documentation Documentation/dev-tools/kasan.rst | 180 ++++++++++++-------- arch/Kconfig | 8 +- arch/arm64/kernel/sleep.S | 2 +- arch/x86/kernel/acpi/wakeup_64.S | 2 +- include/linux/kasan.h | 253 +++++++++++++++++++++------ include/linux/mm.h | 22 ++- kernel/fork.c | 2 +- mm/kasan/common.c | 274 ++++++++++++++++++------------ mm/kasan/generic.c | 27 +-- mm/kasan/hw_tags.c | 183 ++++++++++++++++---- mm/kasan/kasan.h | 113 ++++++++---- mm/kasan/quarantine.c | 13 +- mm/kasan/report.c | 61 ++++--- mm/kasan/report_hw_tags.c | 2 +- mm/kasan/report_sw_tags.c | 13 +- mm/kasan/shadow.c | 5 +- mm/kasan/sw_tags.c | 17 +- mm/mempool.c | 2 +- mm/slab_common.c | 13 +- 19 files changed, 826 insertions(+), 366 deletions(-) -- 2.29.2.222.g5d2a92d10f8-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-10 22:20 UTC|newest] Thread overview: 166+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-10 22:20 Andrey Konovalov [this message] 2020-11-10 22:20 ` [PATCH v2 00/20] kasan: boot parameters for hardware tag-based mode Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` [PATCH v2 01/20] kasan: simplify quarantine_put call site Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:08 ` Marco Elver 2020-11-11 16:08 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 02/20] kasan: rename get_alloc/free_info Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:09 ` Marco Elver 2020-11-11 16:09 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 03/20] kasan: introduce set_alloc_info Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:10 ` Marco Elver 2020-11-11 16:10 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 04/20] kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:13 ` Marco Elver 2020-11-11 16:13 ` Marco Elver 2020-11-12 9:51 ` Catalin Marinas 2020-11-12 9:51 ` Catalin Marinas 2020-11-12 19:38 ` Andrey Konovalov 2020-11-12 19:38 ` Andrey Konovalov 2020-11-12 19:38 ` Andrey Konovalov 2020-11-10 22:20 ` [PATCH v2 05/20] kasan: allow VMAP_STACK for HW_TAGS mode Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:20 ` Marco Elver 2020-11-11 16:20 ` Marco Elver 2020-11-12 0:24 ` Andrey Konovalov 2020-11-12 0:24 ` Andrey Konovalov 2020-11-12 0:24 ` Andrey Konovalov 2020-11-12 10:31 ` Catalin Marinas 2020-11-12 10:31 ` Catalin Marinas 2020-11-10 22:20 ` [PATCH v2 06/20] kasan: remove __kasan_unpoison_stack Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:42 ` Marco Elver 2020-11-11 16:42 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 07/20] kasan: inline kasan_reset_tag for tag-based modes Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:54 ` Marco Elver 2020-11-11 16:54 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 08/20] kasan: inline random_tag for HW_TAGS Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 17:02 ` Marco Elver 2020-11-11 17:02 ` Marco Elver 2020-11-12 0:21 ` Andrey Konovalov 2020-11-12 0:21 ` Andrey Konovalov 2020-11-12 0:21 ` Andrey Konovalov 2020-11-10 22:20 ` [PATCH v2 09/20] kasan: inline kasan_poison_memory and check_invalid_free Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 17:50 ` Marco Elver 2020-11-11 17:50 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 10/20] kasan: inline and rename kasan_unpoison_memory Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 17:49 ` Marco Elver 2020-11-11 17:49 ` Marco Elver 2020-11-12 19:45 ` Andrey Konovalov 2020-11-12 19:45 ` Andrey Konovalov 2020-11-12 19:45 ` Andrey Konovalov 2020-11-12 19:52 ` Marco Elver 2020-11-12 19:52 ` Marco Elver 2020-11-12 19:52 ` Marco Elver 2020-11-12 20:54 ` Andrey Konovalov 2020-11-12 20:54 ` Andrey Konovalov 2020-11-12 20:54 ` Andrey Konovalov 2020-11-12 22:20 ` Marco Elver 2020-11-12 22:20 ` Marco Elver 2020-11-12 22:20 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 11/20] kasan: add and integrate kasan boot parameters Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 18:29 ` Marco Elver 2020-11-11 18:29 ` Marco Elver 2020-11-12 19:51 ` Andrey Konovalov 2020-11-12 19:51 ` Andrey Konovalov 2020-11-12 19:51 ` Andrey Konovalov 2020-11-12 11:35 ` Catalin Marinas 2020-11-12 11:35 ` Catalin Marinas 2020-11-12 11:53 ` Marco Elver 2020-11-12 11:53 ` Marco Elver 2020-11-12 11:53 ` Marco Elver 2020-11-12 12:54 ` Catalin Marinas 2020-11-12 12:54 ` Catalin Marinas 2020-11-12 19:52 ` Andrey Konovalov 2020-11-12 19:52 ` Andrey Konovalov 2020-11-12 19:52 ` Andrey Konovalov 2020-11-13 17:52 ` Marco Elver 2020-11-13 17:52 ` Marco Elver 2020-11-13 17:55 ` Marco Elver 2020-11-13 17:55 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 12/20] kasan, mm: check kasan_enabled in annotations Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 14:48 ` Marco Elver 2020-11-11 14:48 ` Marco Elver 2020-11-11 14:48 ` Marco Elver 2020-11-12 0:36 ` Andrey Konovalov 2020-11-12 0:36 ` Andrey Konovalov 2020-11-12 0:36 ` Andrey Konovalov 2020-11-10 22:20 ` [PATCH v2 13/20] kasan: simplify kasan_poison_kfree Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 18:42 ` Marco Elver 2020-11-11 18:42 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 14/20] kasan, mm: rename kasan_poison_kfree Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 18:53 ` Marco Elver 2020-11-11 18:53 ` Marco Elver 2020-11-12 1:05 ` Andrey Konovalov 2020-11-12 1:05 ` Andrey Konovalov 2020-11-12 1:05 ` Andrey Konovalov 2020-11-10 22:20 ` [PATCH v2 15/20] kasan: don't round_up too much Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 19:08 ` Marco Elver 2020-11-11 19:08 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 16/20] kasan: simplify assign_tag and set_tag calls Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 19:17 ` Marco Elver 2020-11-11 19:17 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 17/20] kasan: clarify comment in __kasan_kfree_large Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 19:18 ` Marco Elver 2020-11-11 19:18 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 18/20] kasan: clean up metadata allocation and usage Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 23:06 ` Marco Elver 2020-11-11 23:06 ` Marco Elver 2020-11-12 20:11 ` Andrey Konovalov 2020-11-12 20:11 ` Andrey Konovalov 2020-11-12 20:11 ` Andrey Konovalov 2020-11-10 22:20 ` [PATCH v2 19/20] kasan, mm: allow cache merging with no metadata Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 15:13 ` Marco Elver 2020-11-11 15:13 ` Marco Elver 2020-11-12 23:00 ` Andrey Konovalov 2020-11-12 23:00 ` Andrey Konovalov 2020-11-12 23:00 ` Andrey Konovalov 2020-11-11 23:27 ` Marco Elver 2020-11-11 23:27 ` Marco Elver 2020-11-10 22:20 ` [PATCH v2 20/20] kasan: update documentation Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-10 22:20 ` Andrey Konovalov 2020-11-11 16:03 ` Marco Elver 2020-11-11 16:03 ` Marco Elver 2020-11-12 0:51 ` Andrey Konovalov 2020-11-12 0:51 ` Andrey Konovalov 2020-11-12 0:51 ` Andrey Konovalov 2020-11-10 22:24 ` [PATCH v2 00/20] kasan: boot parameters for hardware tag-based mode Andrey Konovalov 2020-11-10 22:24 ` Andrey Konovalov 2020-11-10 22:24 ` Andrey Konovalov
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=cover.1605046662.git.andreyknvl@google.com \ --to=andreyknvl@google.com \ --cc=Branislav.Rankov@arm.com \ --cc=akpm@linux-foundation.org \ --cc=aryabinin@virtuozzo.com \ --cc=catalin.marinas@arm.com \ --cc=dvyukov@google.com \ --cc=elver@google.com \ --cc=eugenis@google.com \ --cc=glider@google.com \ --cc=kasan-dev@googlegroups.com \ --cc=kevin.brodsky@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=vincenzo.frascino@arm.com \ --cc=will.deacon@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: linkBe 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.