From: Andrew Morton <akpm@linux-foundation.org>
To: Waiman Long <llong@redhat.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
Nico Pache <npache@redhat.com>
Subject: Re: [PATCH] kasan: Don't call find_vm_area() in RT kernel
Date: Tue, 11 Feb 2025 16:20:19 -0800 [thread overview]
Message-ID: <20250211162019.c2ce0583060cedbd5db199e5@linux-foundation.org> (raw)
In-Reply-To: <6b6c1245-f6ee-4af7-b463-e8b6da60c661@redhat.com>
On Tue, 11 Feb 2025 19:16:34 -0500 Waiman Long <llong@redhat.com> wrote:
> > Fixes: c056a364e954 ("kasan: print virtual mapping info in reports")
> > Cc: <stable@vger.kernel.org>
> >
> > but c056a364e954 is 3 years old and I don't think we care about -rt in
> > such old kernels. Thoughts?
>
> The KASAN report_lock was changed to a raw_spinlock_t in v6.13 kernel
> with commit e30a0361b851 ("kasan: make report_lock a raw spinlock") to
> fix a similar RT problem. The report_lock is acquired before calling
> print_address_description(). Before commit e30a0361b851, this
> find_vm_area() is a secondary issue. We may consider commit e30a0361b851
> isn't complete and this is a fix for that.
Great, thanks, updated...
next prev parent reply other threads:[~2025-02-12 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 16:07 Waiman Long
2025-02-11 22:57 ` Andrew Morton
2025-02-11 23:24 ` Steven Rostedt
2025-02-12 0:16 ` Waiman Long
2025-02-12 0:20 ` Andrew Morton [this message]
2025-02-12 11:59 ` Andrey Ryabinin
2025-02-12 13:34 ` Waiman Long
2025-02-12 17:52 ` Andrey Ryabinin
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=20250211162019.c2ce0583060cedbd5db199e5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=llong@redhat.com \
--cc=npache@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ryabinin.a.a@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