From: Baoquan He <bhe@redhat.com>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
andreyknvl@gmail.com
Cc: sohil.mehta@intel.com, baohua@kernel.org, david@redhat.com,
kbingham@kernel.org, weixugc@google.com, Liam.Howlett@oracle.com,
alexandre.chartre@oracle.com, kas@kernel.org,
mark.rutland@arm.com, trintaeoitogc@gmail.com,
axelrasmussen@google.com, yuanchu@google.com, joey.gouly@arm.com,
samitolvanen@google.com, joel.granados@kernel.org,
graf@amazon.com, vincenzo.frascino@arm.com, kees@kernel.org,
ardb@kernel.org, thiago.bauermann@linaro.org, glider@google.com,
thuth@redhat.com, kuan-ying.lee@canonical.com,
pasha.tatashin@soleen.com, nick.desaulniers+lkml@gmail.com,
vbabka@suse.cz, kaleshsingh@google.com, justinstitt@google.com,
catalin.marinas@arm.com, alexander.shishkin@linux.intel.com,
samuel.holland@sifive.com, dave.hansen@linux.intel.com,
corbet@lwn.net, xin@zytor.com, dvyukov@google.com,
tglx@linutronix.de, scott@os.amperecomputing.com,
jason.andryuk@amd.com, morbo@google.com, nathan@kernel.org,
lorenzo.stoakes@oracle.com, mingo@redhat.com, brgerst@gmail.com,
kristina.martsenko@arm.com, bigeasy@linutronix.de,
luto@kernel.org, jgross@suse.com, jpoimboe@kernel.org,
urezki@gmail.com, mhocko@suse.com, ada.coupriediaz@arm.com,
hpa@zytor.com, leitao@debian.org, peterz@infradead.org,
wangkefeng.wang@huawei.com, surenb@google.com, ziy@nvidia.com,
smostafa@google.com, ryabinin.a.a@gmail.com, ubizjak@gmail.com,
jbohac@suse.cz, broonie@kernel.org, akpm@linux-foundation.org,
guoweikang.kernel@gmail.com, rppt@kernel.org, pcc@google.com,
jan.kiszka@siemens.com, nicolas.schier@linux.dev,
will@kernel.org, andreyknvl@gmail.com, jhubbard@nvidia.com,
bp@alien8.de, x86@kernel.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, llvm@lists.linux.dev,
linux-kbuild@vger.kernel.org, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 17/19] mm: Unpoison pcpu chunks with base address tag
Date: Sat, 13 Sep 2025 16:29:15 +0800 [thread overview]
Message-ID: <aMUrW1Znp1GEj7St@MiWiFi-R3L-srv> (raw)
In-Reply-To: <bcf18f220ef3b40e02f489fdb90fc7a5a153a383.1756151769.git.maciej.wieczor-retman@intel.com>
Hi ,
On 08/25/25 at 10:24pm, Maciej Wieczor-Retman wrote:
> The problem presented here is related to NUMA systems and tag-based
> KASAN mode. It can be explained in the following points:
>
> 1. There can be more than one virtual memory chunk.
> 2. Chunk's base address has a tag.
> 3. The base address points at the first chunk and thus inherits
> the tag of the first chunk.
> 4. The subsequent chunks will be accessed with the tag from the
> first chunk.
> 5. Thus, the subsequent chunks need to have their tag set to
> match that of the first chunk.
>
> Refactor code by moving it into a helper in preparation for the actual
> fix.
I got a boot breakage on a hpe-apollo arm64 system with sw_tags mode, and
the boot breakage can be met stably. The detailed situation is reported
in below link:
System is broken in KASAN sw_tags mode during bootup
https://lore.kernel.org/all/aKMLgHdTOEf9B92E@MiWiFi-R3L-srv/T/#u
After applying this patch 17 and patch 18 in this series, I can confirm
the breakage is gone. Thanks for the great fix, and please feel free to
add:
Tested-by: Baoquan He <bhe@redhat.com>
========================
CONFIG_KASAN=y
CONFIG_CC_HAS_KASAN_MEMINTRINSIC_PREFIX=y
# CONFIG_KASAN_GENERIC is not set
CONFIG_KASAN_SW_TAGS=y
# CONFIG_KASAN_HW_TAGS is not set
# CONFIG_KASAN_OUTLINE is not set
CONFIG_KASAN_INLINE=y
CONFIG_KASAN_STACK=y
CONFIG_KASAN_VMALLOC=y
CONFIG_KASAN_KUNIT_TEST=m
================================
[ 100.907469] ==================================================================
[ 100.907485] BUG: KASAN: invalid-access in pcpu_alloc_noprof+0x42c/0x9a8
[ 100.907509] Write of size 160 at addr 10fffd7fbdc00000 by task systemd/1
[ 100.907524] Pointer tag: [10], memory tag: [5b]
[ 100.907532]
[ 100.907544] CPU: 229 UID: 0 PID: 1 Comm: systemd Not tainted 6.16.0+ #2 PREEMPT(voluntary)
[ 100.907562] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020
[ 100.907571] Call trace:
[ 100.907578] show_stack+0x30/0x98 (C)
[ 100.907597] dump_stack_lvl+0x7c/0xa0
[ 100.907614] print_address_description.isra.0+0x90/0x2b8
[ 100.907635] print_report+0x120/0x208
[ 100.907651] kasan_report+0xc8/0x110
[ 100.907669] kasan_check_range+0x80/0xa0
[ 100.907685] __asan_memset+0x30/0x68
[ 100.907700] pcpu_alloc_noprof+0x42c/0x9a8
[ 100.907716] css_rstat_init+0x1bc/0x220
[ 100.907734] cgroup_create+0x188/0x540
[ 100.907749] cgroup_mkdir+0xb4/0x330
[ 100.907765] kernfs_iop_mkdir+0xb0/0x120
[ 100.907783] vfs_mkdir+0x250/0x380
[ 100.907800] do_mkdirat+0x254/0x298
[ 100.907815] __arm64_sys_mkdirat+0x80/0xc0
[ 100.907831] invoke_syscall.constprop.0+0x88/0x148
[ 100.907848] el0_svc_common.constprop.0+0x78/0x148
[ 100.907863] do_el0_svc+0x38/0x50
[ 100.907877] el0_svc+0x3c/0x160
[ 100.907895] el0t_64_sync_handler+0x10c/0x138
[ 100.907911] el0t_64_sync+0x1b0/0x1b8
[ 100.907925]
[ 100.907931] The buggy address belongs to a 0-page vmalloc region starting at 0x5bfffd7fbdc00000 allocated at pcpu_get_vm_areas+0x0/0x1da8
[ 100.907963] The buggy address belongs to the physical page:
[ 100.907970] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8811a35
[ 100.907984] flags: 0xa6a00000000000(node=1|zone=2|kasantag=0x6a)
[ 100.908006] raw: 00a6a00000000000 0000000000000000 dead000000000122 0000000000000000
[ 100.908019] raw: 0000000000000000 b4ff00878bce6400 00000001ffffffff 0000000000000000
[ 100.908029] raw: 00000000000fffff 0000000000000000
[ 100.908037] page dumped because: kasan: bad access detected
[ 100.908044]
[ 100.908048] Memory state around the buggy address:
[ 100.908059] Unable to handle kernel paging request at virtual address ffff7fd7fbdbffe0
[ 100.908068] KASAN: probably wild-memory-access in range [0xfffffd7fbdbffe00-0xfffffd7fbdbffe0f]
[ 100.908078] Mem abort info:
[ 100.908083] ESR = 0x0000000096000007
[ 100.908089] EC = 0x25: DABT (current EL), IL = 32 bits
[ 100.908098] SET = 0, FnV = 0
[ 100.908105] EA = 0, S1PTW = 0
[ 100.908111] FSC = 0x07: level 3 translation fault
[ 100.908118] Data abort info:
[ 100.908123] ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000
[ 100.908130] CM = 0, WnR = 0, TnD = 0, TagAccess = 0
[ 100.908138] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[ 100.908147] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000008ff8b76000
[ 100.908156] [ffff7fd7fbdbffe0] pgd=1000008ff0299403, p4d=1000008ff0299403, pud=1000008ff0298403, pmd=1000008811a17403, pte=0000000000000000
[ 100.908192] Internal error: Oops: 0000000096000007 [#1] SMP
[ 101.185060] Modules linked in: i2c_dev
[ 101.188820] CPU: 229 UID: 0 PID: 1 Comm: systemd Not tainted 6.16.0+ #2 PREEMPT(voluntary)
[ 101.197175] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.16 07/29/2020
[ 101.206912] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 101.213877] pc : __pi_memcpy_generic+0x24/0x230
[ 101.218418] lr : kasan_metadata_fetch_row+0x20/0x30
[ 101.223299] sp : ffff8000859b7700
[ 101.226610] x29: ffff8000859b7700 x28: 0000000000000100 x27: ffff008ec6291800
[ 101.233758] x26: 00000000000000a0 x25: 0000000000000000 x24: fffffd7fbdbfff00
[ 101.240904] x23: ffff8000826b1e58 x22: fffffd7fbdc00000 x21: 00000000fffffffe
[ 101.248051] x20: ffff800082669d18 x19: fffffd7fbdbffe00 x18: 0000000000000000
[ 101.255196] x17: 3030303030303030 x16: 2066666666666666 x15: 6631303030303030
[ 101.262342] x14: 0000000000000001 x13: 0000000000000001 x12: 0000000000000001
[ 101.269487] x11: 687420646e756f72 x10: 0000000000000020 x9 : 0000000000000000
[ 101.276633] x8 : ffff78000859b76a x7 : 0000000000000000 x6 : 000000000000003a
[ 101.283778] x5 : ffff8000859b7768 x4 : ffff7fd7fbdbfff0 x3 : efff800000000000
[ 101.290924] x2 : 0000000000000010 x1 : ffff7fd7fbdbffe0 x0 : ffff8000859b7758
[ 101.298070] Call trace:
[ 101.300512] __pi_memcpy_generic+0x24/0x230 (P)
[ 101.305051] print_report+0x180/0x208
[ 101.308719] kasan_report+0xc8/0x110
[ 101.312299] kasan_check_range+0x80/0xa0
[ 101.316227] __asan_memset+0x30/0x68
[ 101.319807] pcpu_alloc_noprof+0x42c/0x9a8
[ 101.323908] css_rstat_init+0x1bc/0x220
[ 101.327749] cgroup_create+0x188/0x540
[ 101.331502] cgroup_mkdir+0xb4/0x330
[ 101.335082] kernfs_iop_mkdir+0xb0/0x120
[ 101.339011] vfs_mkdir+0x250/0x380
[ 101.342416] do_mkdirat+0x254/0x298
[ 101.345908] __arm64_sys_mkdirat+0x80/0xc0
[ 101.350008] invoke_syscall.constprop.0+0x88/0x148
[ 101.354803] el0_svc_common.constprop.0+0x78/0x148
[ 101.359598] do_el0_svc+0x38/0x50
[ 101.362916] el0_svc+0x3c/0x160
[ 101.366061] el0t_64_sync_handler+0x10c/0x138
[ 101.370423] el0t_64_sync+0x1b0/0x1b8
[ 101.374095] Code: f100805f 540003c8 f100405f 540000c3 (a9401c26)
[ 101.380187] ---[ end trace 0000000000000000 ]---
[ 101.384802] note: systemd[1] ex
** replaying previous printk message **
>
> Signed-off-by: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
> ---
> Changelog v4:
> - Redo the patch message numbered list.
> - Do the refactoring in this patch and move additions to the next new
> one.
>
> Changelog v3:
> - Remove last version of this patch that just resets the tag on
> base_addr and add this patch that unpoisons all areas with the same
> tag instead.
>
> include/linux/kasan.h | 10 ++++++++++
> mm/kasan/hw_tags.c | 11 +++++++++++
> mm/kasan/shadow.c | 10 ++++++++++
> mm/vmalloc.c | 4 +---
> 4 files changed, 32 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/kasan.h b/include/linux/kasan.h
> index 7a2527794549..3ec432d7df9a 100644
> --- a/include/linux/kasan.h
> +++ b/include/linux/kasan.h
> @@ -613,6 +613,13 @@ static __always_inline void kasan_poison_vmalloc(const void *start,
> __kasan_poison_vmalloc(start, size);
> }
>
> +void __kasan_unpoison_vmap_areas(struct vm_struct **vms, int nr_vms);
> +static __always_inline void kasan_unpoison_vmap_areas(struct vm_struct **vms, int nr_vms)
> +{
> + if (kasan_enabled())
> + __kasan_unpoison_vmap_areas(vms, nr_vms);
> +}
> +
> #else /* CONFIG_KASAN_VMALLOC */
>
> static inline void kasan_populate_early_vm_area_shadow(void *start,
> @@ -637,6 +644,9 @@ static inline void *kasan_unpoison_vmalloc(const void *start,
> static inline void kasan_poison_vmalloc(const void *start, unsigned long size)
> { }
>
> +static inline void kasan_unpoison_vmap_areas(struct vm_struct **vms, int nr_vms)
> +{ }
> +
> #endif /* CONFIG_KASAN_VMALLOC */
>
> #if (defined(CONFIG_KASAN_GENERIC) || defined(CONFIG_KASAN_SW_TAGS)) && \
> diff --git a/mm/kasan/hw_tags.c b/mm/kasan/hw_tags.c
> index 9a6927394b54..1f569df313c3 100644
> --- a/mm/kasan/hw_tags.c
> +++ b/mm/kasan/hw_tags.c
> @@ -382,6 +382,17 @@ void __kasan_poison_vmalloc(const void *start, unsigned long size)
> */
> }
>
> +void __kasan_unpoison_vmap_areas(struct vm_struct **vms, int nr_vms)
> +{
> + int area;
> +
> + for (area = 0 ; area < nr_vms ; area++) {
> + vms[area]->addr = __kasan_unpoison_vmalloc(
> + vms[area]->addr, vms[area]->size,
> + KASAN_VMALLOC_PROT_NORMAL);
> + }
> +}
> +
> #endif
>
> void kasan_enable_hw_tags(void)
> diff --git a/mm/kasan/shadow.c b/mm/kasan/shadow.c
> index d2c70cd2afb1..b41f74d68916 100644
> --- a/mm/kasan/shadow.c
> +++ b/mm/kasan/shadow.c
> @@ -646,6 +646,16 @@ void __kasan_poison_vmalloc(const void *start, unsigned long size)
> kasan_poison(start, size, KASAN_VMALLOC_INVALID, false);
> }
>
> +void __kasan_unpoison_vmap_areas(struct vm_struct **vms, int nr_vms)
> +{
> + int area;
> +
> + for (area = 0 ; area < nr_vms ; area++) {
> + kasan_poison(vms[area]->addr, vms[area]->size,
> + arch_kasan_get_tag(vms[area]->addr), false);
> + }
> +}
> +
> #else /* CONFIG_KASAN_VMALLOC */
>
> int kasan_alloc_module_shadow(void *addr, size_t size, gfp_t gfp_mask)
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index c93893fb8dd4..00be0abcaf60 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -4847,9 +4847,7 @@ struct vm_struct **pcpu_get_vm_areas(const unsigned long *offsets,
> * With hardware tag-based KASAN, marking is skipped for
> * non-VM_ALLOC mappings, see __kasan_unpoison_vmalloc().
> */
> - for (area = 0; area < nr_vms; area++)
> - vms[area]->addr = kasan_unpoison_vmalloc(vms[area]->addr,
> - vms[area]->size, KASAN_VMALLOC_PROT_NORMAL);
> + kasan_unpoison_vmap_areas(vms, nr_vms);
>
> kfree(vas);
> return vms;
> --
> 2.50.1
>
>
next prev parent reply other threads:[~2025-09-13 8:29 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 20:24 [PATCH v5 00/19] kasan: x86: arm64: KASAN tag-based mode for x86 Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 01/19] kasan: sw_tags: Use arithmetic shift for shadow computation Maciej Wieczor-Retman
2025-08-26 19:35 ` Catalin Marinas
2025-08-27 6:26 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 02/19] kasan: sw_tags: Support tag widths less than 8 bits Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 03/19] kasan: Fix inline mode for x86 tag-based mode Maciej Wieczor-Retman
2025-09-06 17:17 ` Andrey Konovalov
2025-08-25 20:24 ` [PATCH v5 04/19] x86: Add arch specific kasan functions Maciej Wieczor-Retman
2025-09-06 17:17 ` Andrey Konovalov
2025-09-08 9:06 ` Maciej Wieczor-Retman
2025-09-18 15:52 ` Andrey Ryabinin
2025-09-19 11:05 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 05/19] kasan: arm64: x86: Make special tags arch specific Maciej Wieczor-Retman
2025-09-06 17:18 ` Andrey Konovalov
2025-09-08 10:12 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 06/19] x86: Reset tag for virtual to physical address conversions Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 07/19] mm: x86: Untag addresses in EXECMEM_ROX related pointer arithmetic Maciej Wieczor-Retman
2025-08-28 9:50 ` Mike Rapoport
2025-08-28 16:22 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 08/19] x86: Physical address comparisons in fill_p*d/pte Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 09/19] x86: KASAN raw shadow memory PTE init Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 10/19] x86: LAM compatible non-canonical definition Maciej Wieczor-Retman
2025-08-25 20:59 ` Samuel Holland
2025-08-27 6:32 ` Maciej Wieczor-Retman
2025-08-25 21:36 ` Dave Hansen
2025-08-26 8:08 ` Maciej Wieczor-Retman
2025-08-27 0:46 ` Samuel Holland
2025-08-27 6:08 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 11/19] x86: LAM initialization Maciej Wieczor-Retman
2025-09-06 22:24 ` Borislav Petkov
2025-09-08 8:30 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 12/19] x86: Minimal SLAB alignment Maciej Wieczor-Retman
2025-09-06 17:18 ` Andrey Konovalov
2025-08-25 20:24 ` [PATCH v5 13/19] kasan: x86: Handle int3 for inline KASAN reports Maciej Wieczor-Retman
2025-09-06 17:19 ` Andrey Konovalov
2025-09-08 10:38 ` Maciej Wieczor-Retman
2025-09-08 12:54 ` Maciej Wieczor-Retman
2025-09-08 13:08 ` Maciej Wieczor-Retman
2025-09-08 20:19 ` Andrey Konovalov
2025-09-09 8:24 ` Maciej Wieczor-Retman
2025-09-09 8:34 ` Peter Zijlstra
2025-09-09 8:40 ` Peter Zijlstra
2025-09-09 8:49 ` Maciej Wieczor-Retman
2025-09-09 9:03 ` Peter Zijlstra
2025-09-10 8:23 ` Maciej Wieczor-Retman
2025-09-09 8:53 ` Maciej Wieczor-Retman
2025-09-09 14:46 ` Andrey Konovalov
2025-08-25 20:24 ` [PATCH v5 14/19] arm64: Unify software tag-based KASAN inline recovery path Maciej Wieczor-Retman
2025-08-26 19:35 ` Catalin Marinas
2025-08-25 20:24 ` [PATCH v5 15/19] kasan: x86: Apply multishot to the inline report handler Maciej Wieczor-Retman
2025-09-06 17:19 ` Andrey Konovalov
2025-09-08 13:02 ` Maciej Wieczor-Retman
2025-09-08 20:19 ` Andrey Konovalov
2025-09-09 8:42 ` Maciej Wieczor-Retman
2025-09-09 14:45 ` Andrey Konovalov
2025-09-09 14:46 ` Andrey Konovalov
2025-08-25 20:24 ` [PATCH v5 16/19] kasan: x86: Logical bit shift for kasan_mem_to_shadow Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 17/19] mm: Unpoison pcpu chunks with base address tag Maciej Wieczor-Retman
2025-09-13 8:29 ` Baoquan He [this message]
2025-09-15 6:29 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 18/19] mm: Unpoison vms[area] addresses with a common tag Maciej Wieczor-Retman
2025-09-06 17:19 ` Andrey Konovalov
2025-09-08 13:11 ` Maciej Wieczor-Retman
2025-09-08 20:19 ` Andrey Konovalov
2025-09-09 8:26 ` Maciej Wieczor-Retman
2025-08-25 20:24 ` [PATCH v5 19/19] x86: Make software tag-based kasan available Maciej Wieczor-Retman
2025-09-06 17:19 ` Andrey Konovalov
2025-09-08 14:11 ` Maciej Wieczor-Retman
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=aMUrW1Znp1GEj7St@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=ada.coupriediaz@arm.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.chartre@oracle.com \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=graf@amazon.com \
--cc=guoweikang.kernel@gmail.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=jason.andryuk@amd.com \
--cc=jbohac@suse.cz \
--cc=jgross@suse.com \
--cc=jhubbard@nvidia.com \
--cc=joel.granados@kernel.org \
--cc=joey.gouly@arm.com \
--cc=jpoimboe@kernel.org \
--cc=justinstitt@google.com \
--cc=kaleshsingh@google.com \
--cc=kas@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=kbingham@kernel.org \
--cc=kees@kernel.org \
--cc=kristina.martsenko@arm.com \
--cc=kuan-ying.lee@canonical.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas.schier@linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=pcc@google.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=samitolvanen@google.com \
--cc=samuel.holland@sifive.com \
--cc=scott@os.amperecomputing.com \
--cc=smostafa@google.com \
--cc=sohil.mehta@intel.com \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=thiago.bauermann@linaro.org \
--cc=thuth@redhat.com \
--cc=trintaeoitogc@gmail.com \
--cc=ubizjak@gmail.com \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--cc=vincenzo.frascino@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
--cc=yuanchu@google.com \
--cc=ziy@nvidia.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