From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Fix validation of EXTRA_CONTEXT signal contexts
Date: Tue, 2 Aug 2022 00:06:17 +0100 [thread overview]
Message-ID: <Yuhcac/iM+WebgW+@sirena.org.uk> (raw)
In-Reply-To: <20220801225926.3694639-1-broonie@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Mon, Aug 01, 2022 at 11:59:26PM +0100, Mark Brown wrote:
> Currently in validate_extra_context() we assert both that the extra data
> pointed to by the EXTRA_CONTEXT is 16 byte aligned and that it immediately
> follows the struct _aarch64_ctx providing the terminator for the linked
I just realised that this is a very similar subject to another fix I
sent for this stuff a few hours ago. Both fixes are needed, the code
really is quite buggy. I've tweaked the subjects locally in case I need
to resend - this one is:
kselftest/arm64: Fix validation of EXTRA_CONTEXT signal contexts
and the other is:
kselftest/arm64: Fix validatation termination record after EXTRA_CONTEXT
The good news is that with the patches I've now posted we no longer get
any spurious failures, though further patches (which should emerge after
the merge window) will be required to actually validate the data inside
an EXTRA_CONTEXT.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-08-01 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 22:59 [PATCH] kselftest/arm64: Fix validation of EXTRA_CONTEXT signal contexts Mark Brown
2022-08-01 23:06 ` Mark Brown [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=Yuhcac/iM+WebgW+@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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