From: linuxtestproject.agent@gmail.com
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] fanotify25: Add CVE reference and include it in CVE runfile
Date: Mon, 13 Jul 2026 16:43:50 +0000 [thread overview]
Message-ID: <20260713164350.3931-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260713155739.48823-1-mdoucha@suse.cz>
Hi Martin,
On Mon, Jul 13 2026, Martin Doucha wrote:
> fanotify25: Add CVE reference and include it in CVE runfile
> + * CVE-2023-52879
> + *
> + * Verify that :manpage:`fanotify(7)` monitoring can be applied to the tracing
> + * filesystem and write events will be correctly delivered. NULL pointer
> + * dereference fixed in:
> + *
> + * commit bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4
> + * Author: Steven Rostedt (Google) <rostedt@goodmis.org>
> + * Date: Tue Oct 31 12:24:53 2023 -0400
> + *
> + * tracing: Have trace_event_file have ref counters
The Author: and Date: lines are commit metadata that do not help
describe what the test does or why it matters. The linux-git tag
already records the commit reference.
Other tests in the tree use a compact inline format, e.g. fanotify24.c:
commit 28bba2c2935e2 ("fsnotify: Pass correct offset to
fsnotify_mmap_perm()")
Would it be possible to drop the Author:/Date: lines and fold the
reference into the description as a single line, e.g.:
NULL pointer dereference fixed in commit bb32500fb9b7
("tracing: Have trace_event_file have ref counters").
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 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 15:57 [LTP] [PATCH] fanotify25: Add CVE reference and include it in CVE runfile Martin Doucha
2026-07-13 16:43 ` linuxtestproject.agent [this message]
2026-07-13 19:24 ` Avinesh Kumar via ltp
2026-07-14 5:41 ` Petr Vorel
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=20260713164350.3931-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