From: linuxtestproject.agent@gmail.com
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] icmp_rate_limit01: Fix rate limit change on older kernels
Date: Wed, 29 Apr 2026 12:26:10 +0000 [thread overview]
Message-ID: <20260429122610.4065-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260429121129.21911-1-mdoucha@suse.cz>
Hi Martin,
On Wed, 29 Apr 2026 14:11:27 +0200, Martin Doucha wrote:
> icmp_rate_limit01: Fix rate limit change on older kernels
> + if (!access("/proc/sys/net/ipv4/icmp_msgs_burst", F_OK))
> + SAFE_FILE_PRINTF("/proc/sys/net/ipv4/icmp_msgs_burst", "50");
SAFE_ACCESS() exists in tst_safe_macros.h, but since it calls tst_brk()
on failure it cannot be used here — file absence is the expected case on
pre-v6.12 kernels and handling it gracefully is the whole point. Is raw
access() acceptable for this feature-probe pattern, or should a different
idiom be used?
Pre-existing issues noticed in the surrounding code (not introduced
by this patch):
- testcases/cve/icmp_rate_limit01.c:203 — sleep(2) in packet_batch()
used to wait for ICMP responses; consider a poll-based approach.
---
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-29 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 12:11 [LTP] [PATCH] icmp_rate_limit01: Fix rate limit change on older kernels Martin Doucha
2026-04-29 12:26 ` linuxtestproject.agent [this message]
2026-05-06 9:12 ` 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=20260429122610.4065-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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