From: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com> To: Andrey Konovalov <andreyknvl@gmail.com> Cc: Samuel Holland <samuel.holland@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, <linux-riscv@lists.infradead.org>, Andrey Ryabinin <ryabinin.a.a@gmail.com>, Alexander Potapenko <glider@google.com>, "Dmitry Vyukov" <dvyukov@google.com>, Vincenzo Frascino <vincenzo.frascino@arm.com>, <kasan-dev@googlegroups.com>, <llvm@lists.linux.dev>, Catalin Marinas <catalin.marinas@arm.com>, <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>, Alexandre Ghiti <alexghiti@rivosinc.com>, Will Deacon <will@kernel.org>, Evgenii Stepanov <eugenis@google.com>, Andrew Morton <akpm@linux-foundation.org>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v2 1/9] kasan: sw_tags: Use arithmetic shift for shadow computation Date: Mon, 10 Feb 2025 16:22:41 +0100 [thread overview] Message-ID: <e7t5yzfw3dq5stp5xjy5yclcx6ikne4vwz7d6w2ukfw2b7gr6t@oomoynf3b2jl> (raw) In-Reply-To: <CA+fCnZeBEe3VWm=VfYvG-f4eh2jAFP-p4Xn4SLEeFCGTudVuEw@mail.gmail.com> On 2024-10-23 at 20:41:57 +0200, Andrey Konovalov wrote: >On Tue, Oct 22, 2024 at 3:59 AM Samuel Holland ><samuel.holland@sifive.com> wrote: ... >> + * Software Tag-Based KASAN, the displacement is signed, so >> + * KASAN_SHADOW_OFFSET is the center of the range. >> */ >> - if (addr < KASAN_SHADOW_OFFSET) >> - return; >> + if (IS_ENABLED(CONFIG_KASAN_GENERIC)) { >> + if (addr < KASAN_SHADOW_OFFSET || >> + addr >= KASAN_SHADOW_OFFSET + max_shadow_size) >> + return; >> + } else { >> + if (addr < KASAN_SHADOW_OFFSET - max_shadow_size / 2 || >> + addr >= KASAN_SHADOW_OFFSET + max_shadow_size / 2) >> + return; > >Hm, I might be wrong, but I think this check does not work. > >Let's say we have non-canonical address 0x4242424242424242 and number >of VA bits is 48. > >Then: > >KASAN_SHADOW_OFFSET == 0xffff800000000000 >kasan_mem_to_shadow(0x4242424242424242) == 0x0423a42424242424 >max_shadow_size == 0x1000000000000000 >KASAN_SHADOW_OFFSET - max_shadow_size / 2 == 0xf7ff800000000000 >KASAN_SHADOW_OFFSET + max_shadow_size / 2 == 0x07ff800000000000 (overflows) > >0x0423a42424242424 is < than 0xf7ff800000000000, so the function will >wrongly return. As I understand this check aims to figure out if the address landed in shadow space and if it didn't we can return. Can't this above snippet be a simple: if (!addr_in_shadow(addr)) return; ? -- Kind regards Maciej Wieczór-Retman
WARNING: multiple messages have this Message-ID (diff)
From: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com> To: Andrey Konovalov <andreyknvl@gmail.com> Cc: Samuel Holland <samuel.holland@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, <linux-riscv@lists.infradead.org>, Andrey Ryabinin <ryabinin.a.a@gmail.com>, Alexander Potapenko <glider@google.com>, "Dmitry Vyukov" <dvyukov@google.com>, Vincenzo Frascino <vincenzo.frascino@arm.com>, <kasan-dev@googlegroups.com>, <llvm@lists.linux.dev>, Catalin Marinas <catalin.marinas@arm.com>, <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>, Alexandre Ghiti <alexghiti@rivosinc.com>, Will Deacon <will@kernel.org>, Evgenii Stepanov <eugenis@google.com>, Andrew Morton <akpm@linux-foundation.org>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v2 1/9] kasan: sw_tags: Use arithmetic shift for shadow computation Date: Mon, 10 Feb 2025 16:22:41 +0100 [thread overview] Message-ID: <e7t5yzfw3dq5stp5xjy5yclcx6ikne4vwz7d6w2ukfw2b7gr6t@oomoynf3b2jl> (raw) In-Reply-To: <CA+fCnZeBEe3VWm=VfYvG-f4eh2jAFP-p4Xn4SLEeFCGTudVuEw@mail.gmail.com> On 2024-10-23 at 20:41:57 +0200, Andrey Konovalov wrote: >On Tue, Oct 22, 2024 at 3:59 AM Samuel Holland ><samuel.holland@sifive.com> wrote: ... >> + * Software Tag-Based KASAN, the displacement is signed, so >> + * KASAN_SHADOW_OFFSET is the center of the range. >> */ >> - if (addr < KASAN_SHADOW_OFFSET) >> - return; >> + if (IS_ENABLED(CONFIG_KASAN_GENERIC)) { >> + if (addr < KASAN_SHADOW_OFFSET || >> + addr >= KASAN_SHADOW_OFFSET + max_shadow_size) >> + return; >> + } else { >> + if (addr < KASAN_SHADOW_OFFSET - max_shadow_size / 2 || >> + addr >= KASAN_SHADOW_OFFSET + max_shadow_size / 2) >> + return; > >Hm, I might be wrong, but I think this check does not work. > >Let's say we have non-canonical address 0x4242424242424242 and number >of VA bits is 48. > >Then: > >KASAN_SHADOW_OFFSET == 0xffff800000000000 >kasan_mem_to_shadow(0x4242424242424242) == 0x0423a42424242424 >max_shadow_size == 0x1000000000000000 >KASAN_SHADOW_OFFSET - max_shadow_size / 2 == 0xf7ff800000000000 >KASAN_SHADOW_OFFSET + max_shadow_size / 2 == 0x07ff800000000000 (overflows) > >0x0423a42424242424 is < than 0xf7ff800000000000, so the function will >wrongly return. As I understand this check aims to figure out if the address landed in shadow space and if it didn't we can return. Can't this above snippet be a simple: if (!addr_in_shadow(addr)) return; ? -- Kind regards Maciej Wieczór-Retman _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-02-10 15:23 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-10-22 1:57 [PATCH v2 0/9] kasan: RISC-V support for KASAN_SW_TAGS using pointer masking Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-22 1:57 ` [PATCH v2 1/9] kasan: sw_tags: Use arithmetic shift for shadow computation Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-23 18:41 ` Andrey Konovalov 2024-10-23 18:41 ` Andrey Konovalov 2025-02-10 15:22 ` Maciej Wieczor-Retman [this message] 2025-02-10 15:22 ` Maciej Wieczor-Retman 2025-02-10 15:52 ` Maciej Wieczor-Retman 2025-02-10 15:52 ` Maciej Wieczor-Retman 2025-02-10 22:57 ` Andrey Konovalov 2025-02-10 22:57 ` Andrey Konovalov 2025-02-11 8:58 ` Maciej Wieczor-Retman 2025-02-11 8:58 ` Maciej Wieczor-Retman 2025-02-11 13:42 ` Maciej Wieczor-Retman 2025-02-11 13:42 ` Maciej Wieczor-Retman 2025-02-11 18:06 ` Maciej Wieczor-Retman 2025-02-11 18:06 ` Maciej Wieczor-Retman 2025-02-13 1:21 ` Andrey Konovalov 2025-02-13 1:21 ` Andrey Konovalov 2025-02-13 1:28 ` Andrey Konovalov 2025-02-13 1:28 ` Andrey Konovalov 2025-02-13 16:20 ` Maciej Wieczor-Retman 2025-02-13 16:20 ` Maciej Wieczor-Retman 2025-02-14 8:20 ` Maciej Wieczor-Retman 2025-02-14 8:20 ` Maciej Wieczor-Retman 2025-02-17 16:13 ` Andrey Konovalov 2025-02-17 16:13 ` Andrey Konovalov 2025-02-17 18:37 ` Maciej Wieczor-Retman 2025-02-17 18:37 ` Maciej Wieczor-Retman 2025-02-17 19:00 ` Andrey Konovalov 2025-02-17 19:00 ` Andrey Konovalov 2024-10-22 1:57 ` [PATCH v2 2/9] kasan: sw_tags: Check kasan_flag_enabled at runtime Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-22 1:57 ` [PATCH v2 3/9] kasan: sw_tags: Support outline stack tag generation Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-23 18:42 ` Andrey Konovalov 2024-10-23 18:42 ` Andrey Konovalov 2024-10-22 1:57 ` [PATCH v2 4/9] kasan: sw_tags: Support tag widths less than 8 bits Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-22 19:30 ` kernel test robot 2024-10-22 19:30 ` kernel test robot 2024-10-22 19:51 ` kernel test robot 2024-10-22 19:51 ` kernel test robot 2024-10-22 1:57 ` [PATCH v2 5/9] riscv: mm: Log potential KASAN shadow alias Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-11-05 13:44 ` Alexandre Ghiti 2024-11-05 13:44 ` Alexandre Ghiti 2024-10-22 1:57 ` [PATCH v2 6/9] riscv: Do not rely on KASAN to define the memory layout Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-11-05 13:47 ` Alexandre Ghiti 2024-11-05 13:47 ` Alexandre Ghiti 2024-10-22 1:57 ` [PATCH v2 7/9] riscv: Align the sv39 linear map to 16 GiB Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-11-05 13:55 ` Alexandre Ghiti 2024-11-05 13:55 ` Alexandre Ghiti 2024-10-22 1:57 ` [PATCH v2 8/9] riscv: Add SBI Firmware Features extension definitions Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-22 1:57 ` [PATCH v2 9/9] riscv: Implement KASAN_SW_TAGS Samuel Holland 2024-10-22 1:57 ` Samuel Holland 2024-10-23 18:42 ` Andrey Konovalov 2024-10-23 18:42 ` 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=e7t5yzfw3dq5stp5xjy5yclcx6ikne4vwz7d6w2ukfw2b7gr6t@oomoynf3b2jl \ --to=maciej.wieczor-retman@intel.com \ --cc=akpm@linux-foundation.org \ --cc=alexghiti@rivosinc.com \ --cc=andreyknvl@gmail.com \ --cc=catalin.marinas@arm.com \ --cc=dvyukov@google.com \ --cc=eugenis@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-mm@kvack.org \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=palmer@dabbelt.com \ --cc=ryabinin.a.a@gmail.com \ --cc=samuel.holland@sifive.com \ --cc=vincenzo.frascino@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: 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.