From: Joey Gouly <joey.gouly@arm.com>
To: <linux-arm-kernel@lists.infradead.org>
Cc: <broonie@kernel.org>, <nd@arm.com>, <catalin.marinas@arm.com>,
<joey.gouly@arm.com>, <will@kernel.org>
Subject: [PATCH v1 0/7] add more tests to MTE kselftests
Date: Tue, 25 Jan 2022 15:09:13 +0000 [thread overview]
Message-ID: <20220125150920.23955-1-joey.gouly@arm.com> (raw)
This is a series which refactors and then adds some extra tests for MTE
in the kselftest framework.
The issue that these tests are for was was fixed by Robin in
295cf156231c ("arm64: Avoid premature usercopy failure") and based on a
simplified example by Catalin [1].
They test some combinations of pointer offsets, sizes and syscalls to
exercise different paths in the kernel.
Thanks,
Joey
[1] https://lore.kernel.org/all/20210624150911.GA25097@arm.com/
Joey Gouly (7):
kselftest/arm64: mte: user_mem: introduce tag_offset and tag_len
kselftest/arm64: mte: user_mem: add tests using tag_offset
kselftest/arm64: mte: user_mem: add test with mte tag inside a page
kselftest/arm64: mte: user_mem: rework error handling
kselftest/arm64: mte: user_mem: check different offsets and sizes
kselftest/arm64: mte: add test type enum
kselftest/arm64: mte: add more test types
.../selftests/arm64/mte/check_user_mem.c | 145 ++++++++++++++----
1 file changed, 112 insertions(+), 33 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-01-25 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 15:09 Joey Gouly [this message]
2022-01-25 15:09 ` [PATCH v1 1/7] kselftest/arm64: mte: user_mem: introduce tag_offset and tag_len Joey Gouly
2022-01-25 15:09 ` [PATCH v1 2/7] kselftest/arm64: mte: user_mem: add tests using tag_offset Joey Gouly
2022-01-25 15:09 ` [PATCH v1 3/7] kselftest/arm64: mte: user_mem: add test with mte tag inside a page Joey Gouly
2022-01-25 15:09 ` [PATCH v1 4/7] kselftest/arm64: mte: user_mem: rework error handling Joey Gouly
2022-01-25 15:09 ` [PATCH v1 5/7] kselftest/arm64: mte: user_mem: check different offsets and sizes Joey Gouly
2022-01-25 16:33 ` Mark Brown
2022-01-26 12:27 ` Joey Gouly
2022-01-25 15:09 ` [PATCH v1 6/7] kselftest/arm64: mte: add test type enum Joey Gouly
2022-01-26 16:33 ` Mark Brown
2022-01-25 15:09 ` [PATCH v1 7/7] kselftest/arm64: mte: add more test types Joey Gouly
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=20220125150920.23955-1-joey.gouly@arm.com \
--to=joey.gouly@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nd@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).