public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] pkey01: Fix TBROK due missing results
Date: Fri, 9 Aug 2024 13:54:56 +0200	[thread overview]
Message-ID: <20240809115456.GB352642@pevik> (raw)
In-Reply-To: <CAEemH2dVqP+r-u6XexYifVAyzNwSdeOsBk-NNrpdWgM3eNssew@mail.gmail.com>

Hi Li, all,

> Hi Petr,

> On Fri, Aug 9, 2024 at 5:55 PM Petr Vorel <pvorel@suse.cz> wrote:

> > PKEY_DISABLE_EXECUTE is ppc64le specific test. Due messages being
> > TINFO test on other archs fails:

> >     tst_test.c:1498: TBROK: Test 2 haven't reported results!


> Ah yes, I think of why I used tst_brk in my previous patch.



> > Changing messages to TCONF. Also exit loop on !execute_supported TCONF
> > (no need to have 30x TCONF with the same error message, because we have
> > PKEY_DISABLE_EXECUTE last). The other TCONF (on MAP_HUGETLB) must be
> > repeated.


> Agreed.


> > Fixes: d2b8a476c2 ("pkey01: Adding test for PKEY_DISABLE_EXECUTE")
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > Hi Li, all,

> > if you don't like PKEY_DISABLE_EXECUTE having to be the last, we can
> > just have 30x TCONF (just to change both TINFO to TCONF). Whatever you
> > prefer.


> It's okay, I guess PKEY_DISABLE_EXECUTE is already the last feature
> for mem protection, READ, WRITE, EXEC, and I don't expect there will
> be a new permission to appear :).

Thanks for a quick ack, merged (with added comment for return value in the
code).

Kind regards,
Petr

> Feel free to add:
> Reviewed-by: Li Wang <liwang@redhat.com>

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2024-08-09 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  9:55 [LTP] [PATCH 1/1] pkey01: Fix TBROK due missing results Petr Vorel
2024-08-09 11:40 ` Li Wang
2024-08-09 11:54   ` Petr Vorel [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=20240809115456.GB352642@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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