From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-stable <stable@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Catalin Marinas <catalin.marinas@arm.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Shuah Khan <shuah@kernel.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: arm64: fp-stress: BUG: KFENCE: memory corruption in fpsimd_release_task
Date: Tue, 16 May 2023 23:45:42 +0900 [thread overview]
Message-ID: <ZGOXFjJnSVz3Lss6@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20230516134447.GB30894@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
On Tue, May 16, 2023 at 02:44:49PM +0100, Will Deacon wrote:
> Mark -- given that this is an SME allocation, please can you take a look?
I'm on holiday.
> I think the implication of the kfence report is that we're writing beyond
> the end of 'task->thread.sme_state' at some point and corrupting the
> redzone.
> There are two reports here, so hopefully it's not too hard to repro.
I think I *once* saw something that might be this but I've never
reproduced it, and I suspect that if this just suddenly came up with
LKFT in stable kernels when there's been no relevant changes AFAIR it's
not showing up terribly reliably there either.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-16 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 6:28 Naresh Kamboju
2023-05-16 13:44 ` Will Deacon
2023-05-16 14:45 ` Mark Brown [this message]
2023-05-22 16:41 ` Will Deacon
2023-05-23 10:49 ` Mark Brown
2023-05-25 13:35 ` Naresh Kamboju
2023-05-25 13:19 ` Naresh Kamboju
2023-05-25 13:47 ` Mark Brown
2023-05-17 19:30 ` Dan Carpenter
2023-05-18 1:52 ` Mark Brown
2023-05-22 15:40 ` Dan Carpenter
2023-05-23 10:28 ` Mark Brown
2023-05-22 22:12 ` Mark Brown
2023-05-25 13:51 ` Naresh Kamboju
2023-06-26 14:41 ` Will Deacon
2023-06-26 17:53 ` Daniel Díaz
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=ZGOXFjJnSVz3Lss6@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=will@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
all inboxes | Powered by JetHome®