From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] sockets/xfrm02: Add ESP-in-TCP page cache corruption test
Date: Wed, 13 May 2026 16:27:41 +0000 [thread overview]
Message-ID: <20260513162741.4013-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260513-fragnesia-v1-1-80c5b3b09005@suse.com>
Hi Andrea,
On 2026-05-13, Andrea Cervesato wrote:
> sockets/xfrm02: Add ESP-in-TCP page cache corruption test
> + acc_fd = SAFE_ACCEPT(srv_fd, NULL, NULL);
> + SAFE_CLOSE(srv_fd);
srv_fd is not reset to -1 after this close. cleanup() checks
`srv_fd != -1` and will double-close the stale descriptor. Add
`srv_fd = -1;` here.
> + file_fd = SAFE_OPEN(TESTFILE, O_WRONLY | O_CREAT, 0444);
> + SAFE_WRITE(SAFE_WRITE_ALL, file_fd, original, DATA_SIZE);
> + SAFE_CLOSE(file_fd);
[...]
> + SAFE_CLOSE(file_fd);
[...]
> + SAFE_CLOSE(file_fd);
Same problem for file_fd: none of the three SAFE_CLOSE calls in run()
reset file_fd to -1, so cleanup() will double-close it. Add
`file_fd = -1;` after each one.
> + splice(pipefd[0], NULL, cli_fd, NULL, DATA_SIZE, 0);
SAFE_SPLICE exists. If failure on patched kernels must be tolerated,
capture the return in a local variable and add a comment explaining
why the error is intentionally ignored.
---
Note:
Our agent completed the review of the patch. The full review can be
found at: https://patchwork.ozlabs.org/project/ltp/list/?series=504173
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-13 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 14:36 [LTP] [PATCH] sockets/xfrm02: Add ESP-in-TCP page cache corruption test Andrea Cervesato
2026-05-13 15:00 ` Cyril Hrubis
2026-05-13 16:27 ` linuxtestproject.agent [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-13 15:35 [LTP] [PATCH v2] " Andrea Cervesato
2026-05-13 16:29 ` [LTP] " linuxtestproject.agent
2026-05-13 16:42 ` Martin Doucha
2026-05-13 17:46 [LTP] [PATCH v3] " Andrea Cervesato
2026-05-13 19: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=20260513162741.4013-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