From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: glider@google.com, andreyknvl@gmail.com, dvyukov@google.com,
vincenzo.frascino@arm.com, akpm@linux-foundation.org,
bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
byungchul@sk.com, max.byungchul.park@gmail.com,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
Yunseong Kim <ysk@kzalloc.com>
Subject: Re: [PATCH] kasan: don't call find_vm_area() in in_interrupt() for possible deadlock
Date: Thu, 3 Jul 2025 19:07:44 +0100 [thread overview]
Message-ID: <aGbG8BIafyR8C0ch@e129823.arm.com> (raw)
In-Reply-To: <1a7f32a8-16ff-406c-9542-8d2ad628d7f4@gmail.com>
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
next prev parent reply other threads:[~2025-07-03 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 20:35 [PATCH] kasan: don't call find_vm_area() in in_interrupt() for possible deadlock Yeoreum Yun
2025-07-02 6:01 ` Byungchul Park
2025-07-02 6:09 ` Byungchul Park
2025-07-02 6:28 ` Yeoreum Yun
2025-07-02 15:46 ` Andrey Ryabinin
2025-07-02 16:04 ` Yeoreum Yun
2025-07-03 17:10 ` Andrey Ryabinin
2025-07-03 18:07 ` Yeoreum Yun [this message]
2025-07-07 7:59 ` Sebastian Andrzej Siewior
2025-07-07 8:07 ` Yeoreum Yun
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=aGbG8BIafyR8C0ch@e129823.arm.com \
--to=yeoreum.yun@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=byungchul@sk.com \
--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=max.byungchul.park@gmail.com \
--cc=rostedt@goodmis.org \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.com \
--cc=ysk@kzalloc.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;
as well as URLs for NNTP newsgroup(s).