Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v7 2/2] connect01: Add negative tests
Date: Wed, 1 Jul 2026 10:38:25 +0200	[thread overview]
Message-ID: <20260701083825.GB477554@pevik> (raw)
In-Reply-To: <20260616093119.8654-3-wegao@suse.com>

Hi Wei,

> Add negative cases for connect(), when errno is EPROTOTYPE or EACCES.
> These error paths were not exercised by the existing test.

...
> @@ -49,6 +62,10 @@ static struct test_case_t {
>  		"connect on a socket found no one listening on remote address"},
>  	{&fd_socket, &sock3, sizeof(sock3), EAFNOSUPPORT,
>  		"address doesn't have the correct address family in sa_family"},
> +	{&fd_unix_dgram, &sock4, sizeof(sock4), EPROTOTYPE,
> +		"socket type does not support the protocol"},
> +	{&fd_unix_stream, &sock4, sizeof(sock4), EACCES,
> +		"write permission is denied on the socket file"},
>  };

>  static int sys_connect(int sockfd, const struct sockaddr *addr,
> @@ -103,6 +120,19 @@ static void setup(void)
>  	sock3.sin_family = 47;
>  	sock3.sin_port = 0;
>  	sock3.sin_addr.s_addr = htonl(0x0AFFFEFD);
> +
> +	sock4.sun_family = AF_UNIX;
> +	strncpy(sock4.sun_path, SOCK_FILE, sizeof(sock4.sun_path));
> +
> +	fd_unix_server = SAFE_SOCKET(AF_UNIX, SOCK_STREAM, 0);
> +	SAFE_BIND(fd_unix_server, (struct sockaddr *)&sock4, sizeof(sock4));
> +	SAFE_CHMOD(SOCK_FILE, 0700);
> +	SAFE_LISTEN(fd_unix_server, 5);
> +
> +	fd_unix_dgram = SAFE_SOCKET(AF_UNIX, SOCK_DGRAM, 0);
> +	fd_unix_stream = SAFE_SOCKET(AF_UNIX, SOCK_STREAM, 0);
> +
> +	pw = SAFE_GETPWNAM("nobody");
>  }

...

> -	TST_EXP_FAIL(sys_connect(*tc->fd, addr, tc->salen),
> -		     tc->exp_errno, "%s", tc->desc);
> +	if (tc->exp_errno == EACCES) {
> +		if (!SAFE_FORK()) {
> +			SAFE_SETUID(pw->pw_uid);
> +			TST_EXP_FAIL(sys_connect(*tc->fd, addr, tc->salen),
> +				     tc->exp_errno, "%s", tc->desc);
> +			exit(0);
> +		}
> +		tst_reap_children();
> +	} else {
> +		TST_EXP_FAIL(sys_connect(*tc->fd, addr, tc->salen),
> +			     tc->exp_errno, "%s", tc->desc);
> +	}

This looks to me way complicated when put into an existing test. Wouldn't be
better to create to add them to a new file (connect03.c)? Please use the style I
introduced in connect01.c (designated initializers, errnos in doc, void =>
struct sockaddr_in, ...).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-07-01  8:38 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 [this message]
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                       ` [LTP] " linuxtestproject.agent
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=20260701083825.GB477554@pevik \
    --to=pvorel@suse.cz \
    --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