[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aGbG8BIafyR8C0ch@e129823.arm.com>
Date: Thu, 3 Jul 2025 19:07:44 +0100
From: Yeoreum Yun <yeoreum.yun@....com>
To: Andrey Ryabinin <ryabinin.a.a@...il.com>
Cc: glider@...gle.com, andreyknvl@...il.com, dvyukov@...gle.com,
vincenzo.frascino@....com, akpm@...ux-foundation.org,
bigeasy@...utronix.de, clrkwllms@...nel.org, rostedt@...dmis.org,
byungchul@...com, max.byungchul.park@...il.com,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-rt-devel@...ts.linux.dev,
Yunseong Kim <ysk@...lloc.com>
Subject: Re: [PATCH] kasan: don't call find_vm_area() in in_interrupt() for
possible deadlock
Hi Andrey,
> [...]
> > Right. unless there is API -- find_vm_area() with spin_trylock(),
> > kasan_find_vm_area() should be removed.
> >
> > But, I'm not sure adding the new API used only bv kasan is better then
> > just remove kasan_find_vm_area().
> >
> > Do you have any idea for this?
> >
>
> I'd say the info from vm_struct is nice to have, but it's not essential for debugging.
> It's probably not worth trying to keep it, so I'd vote for for removing kasan_find_vm_area().
Thanks for sharing. I'll respin with it.
--
Sincerely,
Yeoreum Yun
Powered by blists - more mailing lists