All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi: Add pkt_sched.h and pkt_cls.h fallbacks
Date: Mon,  6 Jul 2026 20:09:20 +0000	[thread overview]
Message-ID: <20260706200920.4295-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260706-cve-2026-46331-v2-1-d5e47a113a84@suse.com>

Hi Andrea,

On Mon, Jul 6 2026 21:12:15 +0200, Andrea Cervesato wrote:
> lapi: Add pkt_sched.h and pkt_cls.h fallbacks

--- [PATCH 2/2] ---

> #include "lapi/sched.h"

lapi/sched.h is not used directly in this file. The CLONE_NEWUSER
and CLONE_NEWNET flags it provides are consumed internally by
tst_setup_netns() in tst_net.c, not here. Neither tst_net.h nor
tst_netdevice.h pulls it in transitively.

The include can be dropped.

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

  reply	other threads:[~2026-07-06 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 19:12 [LTP] [PATCH v2 0/2] Reproducer for cve-2026-46331 Andrea Cervesato
2026-07-06 19:12 ` [LTP] [PATCH v2 1/2] lapi: Add pkt_sched.h and pkt_cls.h fallbacks Andrea Cervesato
2026-07-06 20:09   ` linuxtestproject.agent [this message]
2026-07-06 19:12 ` [LTP] [PATCH v2 2/2] cve: Add act_pedit page-cache corruption test Andrea Cervesato
  -- strict thread matches above, loose matches on Subject: below --
2026-07-06 12:56 [LTP] [PATCH 1/2] lapi: Add pkt_sched.h and pkt_cls.h fallbacks Andrea Cervesato
2026-07-06 14:32 ` [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=20260706200920.4295-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.