Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] connect03: New test case for EPROTOTYPE and EACCES errors
Date: Mon,  6 Jul 2026 08:22:12 +0000	[thread overview]
Message-ID: <20260706082212.4080-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260706060244.23332-1-wegao@suse.com>

Hi Wei,

On Mon, 06 Jul 2026 06:02:34 +0000, Wei Gao <wegao@suse.com> wrote:
> connect03: New test case for EPROTOTYPE and EACCES errors

> Add a new connect03 test case targeting AF_UNIX-specific connect(2)
> error paths, specifically EPROTOTYPE and EACCES.
>
> - EPROTOTYPE is verified by attempting to connect a UNIX domain SOCK_DGRAM
>   socket to a SOCK_STREAM listening server.
> - EACCES is verified by modifying permissions on the socket file to 0700,
>   spawning a child process, dropping privileges to the unprivileged "nobody"
>   user, and attempting to connect.

The body describes the mechanics of both test cases, but does not state
why this new test is needed -- what gap does it fill? Does connect01 or
connect02 already cover AF_UNIX-specific error paths?

Rule 2 in the LTP commit-message guidelines requires the body to state
the motivation or problem being solved, not just what was changed.
A sentence like "connect01/02 only cover generic socket error paths and
do not test AF_UNIX-specific errors" would satisfy this.

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  8:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  4:51 [LTP] [PATCH v2 1/2] connect01: Convert to new API Yang Xu via ltp
2024-05-14  4:51 ` [LTP] [PATCH v2 2/2] connect01: Add negative tests Yang Xu via ltp
2024-07-17 12:30 ` [LTP] [PATCH v2 1/2] connect01: Convert to new API Cyril Hrubis
2026-05-25  9:02 ` [LTP] [PATCH v3 0/2] " Wei Gao via ltp
2026-05-25  9:02   ` [LTP] [PATCH v3 1/2] " Wei Gao via ltp
2026-05-25 10:12     ` [LTP] " linuxtestproject.agent
2026-05-28  4:43       ` Wei Gao via ltp
2026-06-04  4:49     ` [LTP] [PATCH v4 0/2] " Wei Gao via ltp
2026-06-04  4:49       ` [LTP] [PATCH v4 1/2] " Wei Gao via ltp
2026-06-04  7:15         ` [LTP] " linuxtestproject.agent
2026-06-16  1:47         ` [LTP] [PATCH v5 0/2] " Wei Gao via ltp
2026-06-16  1:47           ` [LTP] [PATCH v5 1/2] " Wei Gao via ltp
2026-06-16  4:07             ` [LTP] " linuxtestproject.agent
2026-06-16  5:24             ` [LTP] [PATCH v6 0/2] " Wei Gao via ltp
2026-06-16  5:24               ` [LTP] [PATCH v6 1/2] " Wei Gao via ltp
2026-06-16  8:35                 ` [LTP] " linuxtestproject.agent
2026-06-16  9:31                 ` [LTP] [PATCH v7 0/2] " Wei Gao via ltp
2026-06-16  9:31                   ` [LTP] [PATCH v7 1/2] " Wei Gao via ltp
2026-06-16 10:12                     ` [LTP] " linuxtestproject.agent
2026-07-01  8:34                     ` [LTP] [PATCH v7 1/2] " Petr Vorel
2026-06-16  9:31                   ` [LTP] [PATCH v7 2/2] connect01: Add negative tests Wei Gao via ltp
2026-07-01  8:38                     ` Petr Vorel
2026-07-06  6:02                     ` [LTP] [PATCH v8] connect03: New test case for EPROTOTYPE and EACCES errors Wei Gao via ltp
2026-07-06  8:22                       ` linuxtestproject.agent [this message]
2026-07-06 23:39                       ` [LTP] [PATCH v9] " Wei Gao via ltp
2026-07-07  3:25                         ` [LTP] " linuxtestproject.agent
2026-06-16  5:24               ` [LTP] [PATCH v6 2/2] connect01: Add negative tests Wei Gao via ltp
2026-06-16  1:47           ` [LTP] [PATCH v5 " Wei Gao via ltp
2026-06-04  4:49       ` [LTP] [PATCH v4 " Wei Gao via ltp
2026-05-25  9:02   ` [LTP] [PATCH v3 " Wei Gao via ltp

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=20260706082212.4080-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=wegao@suse.com \
    /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