[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250211162019.c2ce0583060cedbd5db199e5@linux-foundation.org>
Date: Tue, 11 Feb 2025 16:20:19 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Waiman Long <llong@...hat.com>
Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>, Alexander Potapenko
<glider@...gle.com>, Andrey Konovalov <andreyknvl@...il.com>, Dmitry Vyukov
<dvyukov@...gle.com>, Vincenzo Frascino <vincenzo.frascino@....com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Clark Williams
<clrkwllms@...nel.org>, Steven Rostedt <rostedt@...dmis.org>,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev, Nico Pache
<npache@...hat.com>
Subject: Re: [PATCH] kasan: Don't call find_vm_area() in RT kernel
On Tue, 11 Feb 2025 19:16:34 -0500 Waiman Long <llong@...hat.com> wrote:
> > Fixes: c056a364e954 ("kasan: print virtual mapping info in reports")
> > Cc: <stable@...r.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...
Powered by blists - more mailing lists