From: Melon Liu <melon1335@163.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux@armlinux.org.uk, lecopzer.chen@mediatek.com,
linux-arm-kernel@lists.infradead.org, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ARM/mm: Fix stack recursion caused by KASAN
Date: Tue, 8 Oct 2024 01:37:42 +0800 [thread overview]
Message-ID: <ZwQcZvU41vcD-Gkt@liu> (raw)
In-Reply-To: <CACRpkdZwmjerZSL+Qxc1_M3ywGPRJAYJCFX7_dfEknDiKtuP8w@mail.gmail.com>
On Mon, Oct 07, 2024 at 12:25:38PM +0200, Linus Walleij wrote:
> On Mon, Oct 7, 2024 at 7:25 AM Melon Liu <melon1335@163.com> wrote:
>
> > When accessing the KASAN shadow area corresponding to the task stack
> > which is in vmalloc space, the stack recursion would occur if the area`s
> > page tables are unpopulated.
> >
> > Calltrace:
> > ...
> > __dabt_svc+0x4c/0x80
> > __asan_load4+0x30/0x88
> > do_translation_fault+0x2c/0x110
> > do_DataAbort+0x4c/0xec
> > __dabt_svc+0x4c/0x80
> > __asan_load4+0x30/0x88
> > do_translation_fault+0x2c/0x110
> > do_DataAbort+0x4c/0xec
> > __dabt_svc+0x4c/0x80
> > sched_setscheduler_nocheck+0x60/0x158
> > kthread+0xec/0x198
> > ret_from_fork+0x14/0x28
> >
> > Fixes: 565cbaad83d ("ARM: 9202/1: kasan: support CONFIG_KASAN_VMALLOC")
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Melon Liu <melon1335@163.org>
>
> Patch looks correct to me:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Can you put the patch into Russell's patch tracker after some
> time for review, if no issues are found, please?
Ok.
Thanks!
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2024-10-07 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 5:23 [PATCH] ARM/mm: Fix stack recursion caused by KASAN Melon Liu
2024-10-07 10:25 ` Linus Walleij
2024-10-07 17:37 ` Melon Liu [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=ZwQcZvU41vcD-Gkt@liu \
--to=melon1335@163.com \
--cc=kasan-dev@googlegroups.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=stable@vger.kernel.org \
/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