From: linuxtestproject.agent@gmail.com
To: Martin Cermak <mcermak@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Fix Valgrind warnings in ioctl_pidfd02
Date: Fri, 17 Apr 2026 09:22:31 +0000 [thread overview]
Message-ID: <20260417092231.3781-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260417082920.1101928-1-mcermak@redhat.com>
Hi Martin,
On Fri, 17 Apr 2026, Martin Cermak wrote:
> Fix Valgrind warnings in ioctl_pidfd02
The subject names ioctl_pidfd02, but the only changed file is
lib/tst_clone.c. Use the component prefix instead:
lib/tst_clone: Fix clone() parent_tid argument when CLONE_PIDFD is used
> This patch also sets ARG4 and ARG5.
No Fixes: tag. Please add one in the trailer pointing to the commit that
introduced the 2-argument clone() fallback in tst_clone.c.
---
Note:
Our agent completed the review of the patch.
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
next prev parent reply other threads:[~2026-04-17 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:29 [LTP] [PATCH] Fix Valgrind warnings in ioctl_pidfd02 Martin Cermak via ltp
2026-04-17 9:22 ` linuxtestproject.agent [this message]
2026-04-17 12:01 ` Cyril Hrubis
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=20260417092231.3781-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=mcermak@redhat.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