From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Chris Chiu <chris.chiu@canonical.com>,
maddy@linux.ibm.com, shuah@kernel.org
Cc: sshegde@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Chiu <chris.chiu@canonical.com>
Subject: Re: [PATCH] selftests/powerpc: Fix exec_prot test failure on Hash MMU
Date: Tue, 15 Sep 2026 13:32:02 +0530 [thread overview]
Message-ID: <v787ymbp.ritesh.list@gmail.com> (raw)
In-Reply-To: <wlsnyvt2.ritesh.list@gmail.com>
Ritesh Harjani (IBM) <ritesh.list@gmail.com> writes:
> So, I think what we need here is:
>
> diff --git a/tools/testing/selftests/powerpc/mm/exec_prot.c b/tools/testing/selftests/powerpc/mm/exec_prot.c
> index db75b2225de1..51ac2f9c14a6 100644
> --- a/tools/testing/selftests/powerpc/mm/exec_prot.c
> +++ b/tools/testing/selftests/powerpc/mm/exec_prot.c
> @@ -167,13 +167,17 @@ static int test(void)
> * Read an instruction word from the address when the page
> * is execute only. This should generate an access fault.
> */
> - fault_code = -1;
> - remaining_faults = 1;
> - printf("Testing read on --x, should fault...");
> - FAIL_IF(mprotect(insns, pgsize, PROT_EXEC) != 0);
> - i = *fault_addr;
> - FAIL_IF(remaining_faults != 0 || !is_fault_expected(fault_code));
> - printf("ok!\n");
> + if (pkeys_supported) {
One quick correction - I think this should be
if (!hash_mmu || pkeys_supported)
> + fault_code = -1;
> + remaining_faults = 1;
> + printf("Testing read on --x, should fault...");
> + FAIL_IF(mprotect(insns, pgsize, PROT_EXEC) != 0);
> + i = *fault_addr;
> + FAIL_IF(remaining_faults != 0 || !is_fault_expected(fault_code));
> + printf("ok!\n");
> + } else {
> + printf("Testing read on --x, skipped on Hash MMU without pkeys\n");
> + }
>
>
-ritesh
prev parent reply other threads:[~2026-09-15 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 5:09 Chris Chiu
2026-09-15 0:00 ` Chris Chiu
2026-09-15 4:37 ` Ritesh Harjani
2026-09-15 8:02 ` Ritesh Harjani [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=v787ymbp.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=chris.chiu@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=sshegde@linux.ibm.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®