From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 2/2] semop04:Refactor with new API
Date: Wed, 15 Mar 2023 19:39:05 +0100 [thread overview]
Message-ID: <20230315183905.GB172450@pevik> (raw)
In-Reply-To: <20230302071555.18420-3-wegao@suse.com>
Hi Wei,
> +// SPDX-License-Identifier: GPL-2.0
Below is "or (at your option) any later version."
=>
// SPDX-License-Identifier: GPL-2.0-or-later
> /*
> - *
> - * Copyright (c) International Business Machines Corp., 2001
> - *
> - * This program is free software; you can redistribute it and/or modify
> - * it under the terms of the GNU General Public License as published by
> - * the Free Software Foundation; either version 2 of the License, or
> - * (at your option) any later version.
> - *
> - * This program is distributed in the hope that it will be useful,
> - * but WITHOUT ANY WARRANTY; without even the implied warranty of
> - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See
> - * the GNU General Public License for more details.
> - *
> - * You should have received a copy of the GNU General Public License
> - * along with this program; if not, write to the Free Software
> - * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
> + * Copyright (c) International Business Machines Corp., 2001
> + * Copyright (C) 2023 Linux Test Project, Inc.
Actually LTP started to work on the file since 2003, i.e.
* Copyright (C) 2003-2023 Linux Test Project, Inc.
> */
> -/*
> - * FILE : sem01.c
> - * DESCRIPTION : Creates a semaphore and two processes. The processes
> - * each go through a loop where they semdown, delay for a
> - * random amount of time, and semup, so they will almost
> - * always be fighting for control of the semaphore.
> - * HISTORY:
> - * 01/15/2001 Paul Larson (plars@us.ibm.com)
> - * -written
> - * 11/09/2001 Manoj Iyer (manjo@ausin.ibm.com)
Probably you should keep these two names (although you can clean formatting a
bit), e.g.:
* Author: 2001 Paul Larson <plars@us.ibm.com>
* Modified: 2001 Manoj Iyer <manjo@ausin.ibm.com>
> - * Modified.
> - * - Removed compiler warnings.
> - * added exit to the end of function main()
...
> -int semup(int semid)
> +static void semup(int semid)
> {
> struct sembuf semops;
> +
> semops.sem_num = 0;
> +
nit: I'd remove this blank line (readability)
> semops.sem_op = 1;
> +
> semops.sem_flg = SEM_UNDO;
> - if (semop(semid, &semops, 1) == -1) {
> - perror("semup");
> - errors++;
> - return 1;
> - }
> - return 0;
> +
> + SAFE_SEMOP(semid, &semops, 1);
> }
> -int semdown(int semid)
> +static void semdown(int semid)
> {
> struct sembuf semops;
> +
> semops.sem_num = 0;
> +
nit: also here remove blank line.
> semops.sem_op = -1;
> +
> semops.sem_flg = SEM_UNDO;
> - if (semop(semid, &semops, 1) == -1) {
> - perror("semdown");
> - errors++;
> - return 1;
> - }
> - return 0;
> +
> + SAFE_SEMOP(semid, &semops, 1);
> }
> -void delayloop()
> +static void delayloop(void)
> {
> int delay;
> +
> delay = 1 + ((100.0 * rand()) / RAND_MAX);
> +
> if (verbose)
> - printf("in delay function for %d microseconds\n", delay);
> + tst_res(TINFO, "in delay function for %d microseconds", delay);
I'd remove this message.
> usleep(delay);
> }
> void mainloop(int semid)
> {
> int i;
> +
> for (i = 0; i < loops; i++) {
> - if (semdown(semid)) {
> - printf("semdown failed\n");
> - }
> + semdown(semid);
> if (verbose)
> - printf("sem is down\n");
> + tst_res(TINFO, "Sem is down");
Actually this message is IMHO useless. semdown() uses SAFE_SEMOP() => we will
see where it failed.
> delayloop();
> - if (semup(semid)) {
> - printf("semup failed\n");
> - }
> + semup(semid);
> if (verbose)
> - printf("sem is up\n");
> + tst_res(TINFO, "Sem is up");
The same applies there => I'd remove verbose and these messages.
> }
> }
> -int main(int argc, char *argv[])
> +static void run(void)
> {
> - int semid, opt;
> + int semid;
> union semun semunion;
> - extern char *optarg;
> pid_t pid;
> int chstat;
> - while ((opt = getopt(argc, argv, "l:vh")) != EOF) {
> - switch ((char)opt) {
> - case 'l':
> - loops = atoi(optarg);
> - break;
> - case 'v':
> - verbose = 1;
> - break;
> - case 'h':
> - default:
> - printf("Usage: -l loops [-v]\n");
> - exit(1);
> - }
> - }
> -
> /* set up the semaphore */
> - if ((semid = semget((key_t) 9142, 1, 0666 | IPC_CREAT)) < 0) {
> - printf("error in semget()\n");
> - exit(-1);
> - }
> + semid = SAFE_SEMGET((key_t) 9142, 1, 0666 | IPC_CREAT);
> + if (semid < 0)
> + tst_brk(TBROK, "Error in semget id=%i", semid);
All safe messages handles error checking and call tst_brk() on error => this if
check is unreachable (useless) => remove it.
> +
> semunion.val = 1;
> - if (semctl(semid, 0, SETVAL, semunion) == -1) {
> - printf("error in semctl\n");
> - }
> - if ((pid = fork()) < 0) {
> - printf("fork error\n");
> - exit(-1);
> - }
> + SAFE_SEMCTL(semid, 0, SETVAL, semunion);
> +
> + pid = SAFE_FORK();
> + if (pid < 0)
> + tst_brk(TBROK, "Fork failed pid %i", pid);
Also this if check is useless => remove it.
> +
> if (pid) {
> /* parent */
> srand(pid);
> @@ -147,18 +109,29 @@ int main(int argc, char *argv[])
> printf("child exited with status\n");
> exit(-1);
> }
NOTE: waitpid(), WIFEXITED(), printf() and exit(-1) here should be replaced by tst_reap_children(), see
https://github.com/linux-test-project/ltp/wiki/C-Test-API#18-doing-the-test-in-the-child-process
91e6a95b7 ("clone08: convert to new LTP API")
> + SAFE_SEMCTL(semid, 0, IPC_RMID, semunion);
> + tst_res(TPASS, "Semaphore up/down check success");
> } else {
> /* child */
> mainloop(semid);
> }
> - exit(0);
> }
> +
> +static void setup(void)
> +{
> + if (opt_loops_str)
> + loops = SAFE_STRTOL(opt_loops_str, 1, INT_MAX);
> +}
I wonder if we need to specify loops, we have -i which can do more runs.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-15 18:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:25 [LTP] [PATCH v1] Move semaphore/ tests to semop/ Wei Gao via ltp
2023-01-19 18:00 ` Petr Vorel
2023-01-20 1:05 ` [LTP] [PATCH v2] " Wei Gao via ltp
2023-02-28 9:15 ` Richard Palethorpe
2023-03-02 7:15 ` [LTP] [PATCH v3 0/2] Refactor semaphore Wei Gao via ltp
2023-03-02 7:15 ` [LTP] [PATCH v3 1/2] Move semaphore/ tests to semop/ Wei Gao via ltp
2023-03-15 12:31 ` Petr Vorel
2023-03-15 13:11 ` Wei Gao via ltp
2023-03-15 17:47 ` Petr Vorel
2023-03-17 12:29 ` Li Wang
2023-03-19 17:05 ` Petr Vorel
2023-03-02 7:15 ` [LTP] [PATCH v3 2/2] semop04:Refactor with new API Wei Gao via ltp
2023-03-15 12:36 ` Petr Vorel
2023-03-15 13:03 ` Wei Gao via ltp
2023-03-15 18:39 ` Petr Vorel [this message]
2023-03-16 7:22 ` [LTP] [PATCH v4 0/2] Refactor semaphore Wei Gao via ltp
2023-03-16 7:22 ` [LTP] [PATCH v4 1/2] Move semaphore/ tests to semop/ Wei Gao via ltp
2023-03-16 7:22 ` [LTP] [PATCH v4 2/2] semop04:Refactor with new API Wei Gao via ltp
2023-05-29 18:34 ` Petr Vorel
2023-05-30 12:07 ` [LTP] [v5,2/2] semop04: Refactor " Wei Gao via ltp
2023-06-21 10:25 ` Petr Vorel
2023-08-29 9:20 ` Richard Palethorpe
2023-08-29 11:00 ` [LTP] [v6,2/2] " Wei Gao via ltp
2023-08-29 11:18 ` [LTP] [v7,2/2] " Wei Gao via ltp
2023-08-30 11:41 ` Andrea Cervesato via ltp
2023-09-01 7:38 ` Richard Palethorpe
2023-09-02 11:32 ` [LTP] [PATCH v8] " 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=20230315183905.GB172450@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