linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej Wieczór-Retman" <m.wieczorretman@pm.me>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: urezki@gmail.com, elver@google.com, vincenzo.frascino@arm.com,
	glider@google.com, dvyukov@google.com, ryabinin.a.a@gmail.com,
	andreyknvl@gmail.com, kasan-dev@googlegroups.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	maciej.wieczor-retman@intel.com,
	Jiayuan Chen <jiayuan.chen@linux.dev>
Subject: Re: [PATCH v2 0/2] kasan: vmalloc: Fix incorrect tag assignment with multiple vm_structs
Date: Tue, 02 Dec 2025 17:13:44 +0000	[thread overview]
Message-ID: <pql2nsktwqkh7olaq7yzh5wtqvnpr6u2mdvtmaqipwwzvomtzo@bilmkfsgxhbo> (raw)
In-Reply-To: <20251202083522.1b0349117b9159b891808532@linux-foundation.org>

On 2025-12-02 at 08:35:22 -0800, Andrew Morton wrote:
>On Tue, 02 Dec 2025 14:27:56 +0000 Maciej Wieczor-Retman <m.wieczorretman@pm.me> wrote:
...
>
>This series overlaps a lot with
>
>https://lkml.kernel.org/r/20251128111516.244497-1-jiayuan.chen@linux.dev
>
>Please discuss!
>

Thanks for pointing it out, I'll test if Jiayuan's version of
__kasan_unpoison_vmalloc fixes the issue I'm seeing.

kind regards
Maciej Wieczór-Retman



      reply	other threads:[~2025-12-02 17:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 14:27 Maciej Wieczor-Retman
2025-12-02 14:29 ` [PATCH v2 1/2] kasan: Refactor pcpu kasan vmalloc unpoison Maciej Wieczor-Retman
2025-12-03 15:53   ` Andrey Konovalov
2025-12-03 16:43     ` Maciej Wieczór-Retman
2025-12-02 14:29 ` [PATCH v2 2/2] kasan: Unpoison vms[area] addresses with a common tag Maciej Wieczor-Retman
2025-12-03 15:53   ` Andrey Konovalov
2025-12-03 16:24     ` Maciej Wieczór-Retman
2025-12-04  0:43       ` Andrey Konovalov
2025-12-04  8:00         ` Maciej Wieczór-Retman
2025-12-02 16:35 ` [PATCH v2 0/2] kasan: vmalloc: Fix incorrect tag assignment with multiple vm_structs Andrew Morton
2025-12-02 17:13   ` Maciej Wieczór-Retman [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=pql2nsktwqkh7olaq7yzh5wtqvnpr6u2mdvtmaqipwwzvomtzo@bilmkfsgxhbo \
    --to=m.wieczorretman@pm.me \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=jiayuan.chen@linux.dev \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=ryabinin.a.a@gmail.com \
    --cc=urezki@gmail.com \
    --cc=vincenzo.frascino@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: 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