From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi: Add pkt_cls.h fallback
Date: Mon, 13 Jul 2026 14:13:50 +0000 [thread overview]
Message-ID: <20260713141350.4119-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260713-cve-2026-46331-v4-1-0089fd01ce62@suse.com>
Hi Andrea,
On Mon, 13 Jul 2026 14:37:07 +0200, Andrea Cervesato wrote:
> lapi: Add pkt_cls.h fallback
--- [PATCH 4/4] ---
> +static int file_fd = -1;
> +static int listen_fd = -1;
> +static int cli_fd = -1;
> +static int acc_fd = -1;
> + SAFE_CLOSE(cli_fd);
> + SAFE_CLOSE(acc_fd);
> + SAFE_CLOSE(file_fd);
> + if (cli_fd != -1)
> + SAFE_CLOSE(cli_fd);
> +
> + if (acc_fd != -1)
> + SAFE_CLOSE(acc_fd);
> +
> + if (file_fd != -1)
> + SAFE_CLOSE(file_fd);
run() closes cli_fd, acc_fd, and file_fd but does not reset them to -1.
cleanup() is always called after run() completes, sees non-(-1) values,
and calls SAFE_CLOSE() a second time. SAFE_CLOSE() calls tst_brk(TBROK)
on EBADF, so the test always ends with TBROK on a clean kernel.
Add reset-to-(-1) after each close in run():
SAFE_CLOSE(cli_fd); cli_fd = -1;
SAFE_CLOSE(acc_fd); acc_fd = -1;
...
SAFE_CLOSE(file_fd); file_fd = -1;
> +#define NETDEV_MAY_REMOVE_QDISC(ifname, family, parent, handle, qd_kind) \
> + tst_netdev_remove_qdisc(__FILE__, __LINE__, 0, (ifname), (family), \
> + (parent), (handle), (qd_kind))
The new macro silently tolerates a missing qdisc (strict=0) while the
existing NETDEV_REMOVE_QDISC fails hard. A short comment before the
definition would clarify that distinction for readers.
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
next prev parent reply other threads:[~2026-07-13 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:37 [LTP] [PATCH v4 0/4] Reproducer for cve-2026-46331 Andrea Cervesato
2026-07-13 12:37 ` [LTP] [PATCH v4 1/4] lapi: Add pkt_cls.h fallback Andrea Cervesato
2026-07-13 14:13 ` linuxtestproject.agent [this message]
2026-07-13 12:37 ` [LTP] [PATCH v4 2/4] lapi: Add pkt_sched.h fallback Andrea Cervesato
2026-07-13 12:37 ` [LTP] [PATCH v4 3/4] lapi: Add tc_pedit.h fallback Andrea Cervesato
2026-07-13 12:37 ` [LTP] [PATCH v4 4/4] cve: Add act_pedit page-cache corruption test Andrea Cervesato
-- strict thread matches above, loose matches on Subject: below --
2026-07-14 8:38 [LTP] [PATCH v5 1/4] lapi: Add pkt_cls.h fallback Andrea Cervesato
2026-07-14 10:53 ` [LTP] " linuxtestproject.agent
2026-07-07 13:42 [LTP] [PATCH v3 1/4] " Andrea Cervesato
2026-07-07 14:28 ` [LTP] " linuxtestproject.agent
2026-07-07 14:53 ` 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=20260713141350.4119-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