From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi: fallback SPLICE_F_MORE
Date: Fri, 8 May 2026 09:26:46 +0000 [thread overview]
Message-ID: <20260508092646.3949-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260508-cve-2026-43284-v1-1-bf2549d2430d@suse.com>
Hi Andrea,
--- [PATCH 1/3] ---
On 2026-05-08, Andrea Cervesato wrote:
> lapi: fallback SPLICE_F_MORE
The commit body is empty. Please add at least one sentence explaining
why this fallback is needed — e.g. which kernel version introduced
SPLICE_F_MORE, or that it is required by the xfrm01 test added later
in this series.
--- [PATCH 2/3] ---
On 2026-05-08, Andrea Cervesato wrote:
> lapi: fallback UDP_ENCAP and UDP_ENCAP_ESPINUDP
Same issue: the commit body is empty. Add a sentence describing why
these constants need a fallback definition.
---
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-05-08 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 9:17 [LTP] [PATCH 0/3] cve-2026-43284 reproducer Andrea Cervesato
2026-05-08 9:17 ` [LTP] [PATCH 1/3] lapi: fallback SPLICE_F_MORE Andrea Cervesato
2026-05-08 9:26 ` linuxtestproject.agent [this message]
2026-05-08 9:28 ` [LTP] " Andrea Cervesato via ltp
2026-05-08 9:17 ` [LTP] [PATCH 2/3] lapi: fallback UDP_ENCAP and UDP_ENCAP_ESPINUDP Andrea Cervesato
2026-05-08 9:17 ` [LTP] [PATCH 3/3] network/sockets: Add xfrm ESP page cache corruption test Andrea Cervesato
2026-05-08 10:18 ` [LTP] [PATCH 0/3] cve-2026-43284 reproducer Ricardo B. Marlière via ltp
2026-05-08 13:41 ` Andrea Cervesato via ltp
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=20260508092646.3949-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=andrea.cervesato@suse.de \
--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