From: Will Deacon <will@kernel.org>
To: yee.lee@mediatek.com, linux-kernel@vger.kernel.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
Kuan-Ying.lee@mediatek.com, nicholas.Tang@mediatek.com,
Matthias Brugger <matthias.bgg@gmail.com>,
Sami Tolvanen <samitolvanen@google.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
chinwen.chang@mediatek.com
Subject: Re: [PATCH v2] scs: Release kasan vmalloc poison in scs_free process
Date: Thu, 30 Sep 2021 09:53:31 +0100 [thread overview]
Message-ID: <163299104851.1259041.949139290018170136.b4-ty@kernel.org> (raw)
In-Reply-To: <20210930081619.30091-1-yee.lee@mediatek.com>
On Thu, 30 Sep 2021 16:16:13 +0800, yee.lee@mediatek.com wrote:
> From: Yee Lee <yee.lee@mediatek.com>
>
> Since scs allocation is moved to vmalloc region, the
> shadow stack is protected by kasan_posion_vmalloc.
> However, the vfree_atomic operation needs to access
> its context for scs_free process and causes kasan error
> as the dump info below.
>
> [...]
Applied to arm64 (for-next/scs), thanks!
[1/1] scs: Release kasan vmalloc poison in scs_free process
https://git.kernel.org/arm64/c/528a4ab45300
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-09-30 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 8:16 yee.lee
2021-09-30 8:35 ` Will Deacon
2021-09-30 9:06 ` Yee Lee
2021-09-30 8:53 ` Will Deacon [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=163299104851.1259041.949139290018170136.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Kuan-Ying.lee@mediatek.com \
--cc=catalin.marinas@arm.com \
--cc=chinwen.chang@mediatek.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nicholas.Tang@mediatek.com \
--cc=samitolvanen@google.com \
--cc=yee.lee@mediatek.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
all inboxes | Powered by JetHome®