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] cve-2026-46331: fix intermittent ENOENT failure
Date: Mon, 20 Jul 2026 15:54:07 +0000	[thread overview]
Message-ID: <20260720155407.3993-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260720-fix_cve-2026-46331_enoent-v2-1-395819e74978@suse.com>

Hi Andrea,

On Mon, 20 Jul 2026 15:17:55 +0200, Andrea Cervesato wrote:
> cve-2026-46331: fix intermittent ENOENT failure

> +	.tags = (const struct tst_tag[]) {
> +		{"linux-git", "899ee91156e5"},
> +		{"CVE", "2026-46331"},
> +		{}
> +	},

The fix commit 899ee91156e5 is not present in kernel 7.2 (the current
latest stable release). Per ground rule 8, the subject line needs a
[STAGING] prefix:

  [STAGING] cve-2026-46331: fix intermittent ENOENT failure

Verdict - Needs revision

Pre-existing issues:

The test entry lives in runtest/cve, but since the fix is not yet in a
released kernel the entry should be in runtest/staging instead. This was
introduced by the original test-addition commit (d6fe8d8e7 "cve: Add
act_pedit page-cache corruption test"), which also lacks the [STAGING]
prefix.

---
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-20 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 13:17 [LTP] [PATCH v2] cve-2026-46331: fix intermittent ENOENT failure Andrea Cervesato
2026-07-20 15:54 ` linuxtestproject.agent [this message]

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=20260720155407.3993-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.