All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Jan Polensky <japo@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] thp04: group runtime state and skip when /proc/self/mem writes are blocked
Date: Tue,  8 Sep 2026 18:26:29 +0000	[thread overview]
Message-ID: <20260908182629.3920-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260908165430.251897-2-japo@linux.ibm.com>

Hi Jan,

On Tue Sep 8 18:54:28 2026 +0200, Jan Polensky <japo@linux.ibm.com> wrote:
> thp04: group runtime state and skip when /proc/self/mem writes are blocked

--- [PATCH 3/3] ---

> +	for (i = 0; i < TEST_ITERATIONS; i++) {
> +		if (*shared->test_ptr != shared->expected_val) {
> +			tst_res(TFAIL,
> +				"Iteration %d: expected 0x%x, got 0x%x",
> +				i, shared->expected_val, *shared->test_ptr);
> +			exit(1);
> +		}
> +
> +		if (i < TEST_ITERATIONS - 1)
> +			raise(SIGSTOP);
> +	}

The condition i < TEST_ITERATIONS - 1 prevents the tracee from stopping on
the last iteration, causing it to exit immediately. The parent's waitpid
sees WIFEXITED and aborts with tst_brk(TBROK). Call raise(SIGSTOP)
unconditionally on all iterations.

> +static void run(void)
> +{
> +	char path[64];

Do not use a custom buffer size for filesystem paths. Use PATH_MAX from
<limits.h>.

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

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

  reply	other threads:[~2026-09-08 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 16:54 [LTP] [PATCH v6 0/3] Handle FORCE_PTRACE in thp04 and add ptrace coverage Jan Polensky
2026-09-08 16:54 ` [LTP] [PATCH v6 1/3] thp04: group runtime state and skip when /proc/self/mem writes are blocked Jan Polensky
2026-09-08 18:26   ` linuxtestproject.agent [this message]
2026-09-08 16:54 ` [LTP] [PATCH v6 2/3] ptrace: add test for /proc/self/mem write rejection Jan Polensky
2026-09-08 16:54 ` [LTP] [PATCH v6 3/3] ptrace: add test for /proc/pid/mem writes under ptrace Jan Polensky
2026-09-09 17:23 ` [LTP] [PATCH v6 0/3] Handle FORCE_PTRACE in thp04 and add ptrace coverage Andrea Cervesato via ltp
  -- strict thread matches above, loose matches on Subject: below --
2026-09-08 11:13 [LTP] [PATCH v5 1/3] thp04: group runtime state and skip when /proc/self/mem writes are blocked Jan Polensky
2026-09-08 15:01 ` [LTP] " linuxtestproject.agent
2026-08-12 13:28 [LTP] [PATCH v4 1/3] " Jan Polensky
2026-08-12 15:01 ` [LTP] " linuxtestproject.agent

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=20260908182629.3920-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=japo@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.