From: Cyril Hrubis <chrubis@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] Add test for UI_GET_NAME ioctl
Date: Thu, 12 Oct 2023 16:05:21 +0200 [thread overview]
Message-ID: <ZSf9IdW9ciTDjkFm@yuki> (raw)
In-Reply-To: <20231012112548.6887-1-wegao@suse.com>
Hi!
> +static int check_ui_get_sysname_ioctl(int fd)
> +{
> + char name[256];
> +
> + SAFE_IOCTL(NULL, fd, UI_GET_SYSNAME(sizeof(name)), name, NULL);
> +
> + DIR *test_dir;
> +
> + struct dirent *ent;
> +
> + test_dir = SAFE_OPENDIR(NULL, "/sys/devices/virtual/input/");
> +
> + while ((ent = SAFE_READDIR(NULL, test_dir))) {
> + if (!strcmp(ent->d_name, name))
> + return 1;
> + else
> + continue;
> + }
Why do we loop over the directory here? Can't we just directly check
that the path /sys/devices/virtual/input/$name/ exists?
I guess that we can as well read the
/sys/devices/virtual/input/$name/dev and match that against fstat() on
the fd.
> + return 0;
> +}
> +
> void create_device(int fd)
> {
> int nb;
> @@ -202,7 +225,7 @@ void create_device(int fd)
> SAFE_IOCTL(NULL, fd, UI_DEV_CREATE, NULL);
>
> for (nb = 100; nb > 0; nb--) {
> - if (check_device())
> + if (check_device() && check_ui_get_sysname_ioctl(fd))
Maybe it would be a bit more readable if we did:
if (check_device() {
check_ui_get_sysname_ioctl(fd);
return;
}
> return;
> usleep(10000);
> }
> --
> 2.35.3
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-12 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 11:13 [LTP] [PATCH v1] Add test for UI_GET_NAME ioctl Wei Gao via ltp
2023-10-12 11:25 ` [LTP] [PATCH v2] " Wei Gao via ltp
2023-10-12 14:05 ` Cyril Hrubis [this message]
2023-10-14 3:36 ` Wei Gao via ltp
2023-10-16 15:49 ` Cyril Hrubis
2023-10-16 23:52 ` Wei Gao via ltp
2023-10-14 3:31 ` [LTP] [PATCH v3] " Wei Gao via ltp
2023-10-17 11:08 ` Cyril Hrubis
2023-10-17 13:16 ` [LTP] [PATCH v4] " Wei Gao via ltp
2023-10-23 14:16 ` Cyril Hrubis
2023-10-24 9:10 ` [LTP] [CI FAILURE] " Petr Vorel
2023-10-24 9:33 ` Cyril Hrubis
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=ZSf9IdW9ciTDjkFm@yuki \
--to=chrubis@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