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: Tue, 14 Jul 2026 10:53:46 +0000 [thread overview]
Message-ID: <20260714105346.3883-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260714-cve-2026-46331-v5-1-bab4ac23c1f7@suse.com>
Hi Andrea,
On Tue, 14 Jul 2026 10:38:58 +0200, Andrea Cervesato wrote:
> lapi: Add pkt_cls.h fallback
--- [PATCH 4/4] ---
> +/*
> + * Same as NETDEV_REMOVE_QDISC() but does not fail when the qdisc is
> + * missing (strict=0), so it can be used to clear a possibly absent qdisc.
> + */
> +#define NETDEV_MAY_REMOVE_QDISC(ifname, family, parent, handle, qd_kind) \
New public macros in include/ require kernel-doc (/** */), not a plain
block comment. The content is fine; it just needs the right opener:
/**
* NETDEV_MAY_REMOVE_QDISC - remove qdisc without failing if absent.
* @ifname: network interface name
* @family: address family
* @parent: parent handle
* @handle: qdisc handle
* @qd_kind: qdisc kind string
*
* Same as NETDEV_REMOVE_QDISC() but passes strict=0, so it does not
* fail when the qdisc is missing.
*/
> +#define NETDEV_REMOVE_QDISC(ifname, family, parent, handle, qd_kind) \
> tst_netdev_remove_qdisc(__FILE__, __LINE__, 1, (ifname), (family), \
> (parent), (handle), (qd_kind))
> +/*
No blank line between the closing of NETDEV_REMOVE_QDISC and the comment
that opens NETDEV_MAY_REMOVE_QDISC. All other macro blocks in the file
have a blank line between them.
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-14 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 8:38 [LTP] [PATCH v5 0/4] Reproducer for cve-2026-46331 Andrea Cervesato
2026-07-14 8:38 ` [LTP] [PATCH v5 1/4] lapi: Add pkt_cls.h fallback Andrea Cervesato
2026-07-14 10:53 ` linuxtestproject.agent [this message]
2026-07-14 8:38 ` [LTP] [PATCH v5 2/4] lapi: Add pkt_sched.h fallback Andrea Cervesato
2026-07-14 8:39 ` [LTP] [PATCH v5 3/4] lapi: Add tc_pedit.h fallback Andrea Cervesato
2026-07-14 8:39 ` [LTP] [PATCH v5 4/4] cve: Add act_pedit page-cache corruption test Andrea Cervesato
-- strict thread matches above, loose matches on Subject: below --
2026-07-13 12:37 [LTP] [PATCH v4 1/4] lapi: Add pkt_cls.h fallback Andrea Cervesato
2026-07-13 14:13 ` [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=20260714105346.3883-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