From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/mkdir09: rewrite in new LTP API
Date: Thu, 27 Jan 2022 15:04:09 +0100 [thread overview]
Message-ID: <YfKmWdNN+G/hjphN@pevik> (raw)
In-Reply-To: <a0733b841c7867ca6af1feb033b691c9f72ce0ec.1643291588.git.jstancek@redhat.com>
Hi Jan,
> 'jump' variable is not initialized, which I suspect is behind
> rare failures of this test. The original test is using longjmp,
> processes and signals to sychronize couple processes that
> exercise mkdir/rmdir calls.
> Rewrite it using threads and new LTP API, drop all parameters,
> because no runtest is using them, and make new default test time
> just 1 second.
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> ---
> It's based on original test, but I question its usefulness,
> since it's just mkdir/rmdir in loop over same directory.
> So, I decided to port it with just 1 second test time, but
> I'm not opposed to dropping this test entirely. Thoughts?
Not sure about usefulness. Also how about use .all_filesystems to have smoke
test for all supported filesystems?
Kind regards,
Petr
+++ testcases/kernel/syscalls/mkdir/mkdir09.c
@@ -14,9 +14,10 @@
#include "tst_test.h"
#include "tst_safe_pthread.h"
+#define MNTPOINT "mntpoint"
#define MODE_RWX 07770
-#define DIR_NAME "./X.%d"
-#define DIR_NAME_GROUP "./X.%d.%d"
+#define DIR_NAME MNTPOINT "/X.%d"
+#define DIR_NAME_GROUP MNTPOINT "/X.%d.%d"
#define NCHILD 3
static int child_groups = 2;
@@ -166,4 +167,7 @@ static struct tst_test test = {
.test_all = verify_mkdir,
.needs_tmpdir = 1,
.setup = setup,
+ .mount_device = 1,
+ .mntpoint = MNTPOINT,
+ .all_filesystems = 1,
};
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-27 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 13:56 [LTP] [PATCH] syscalls/mkdir09: rewrite in new LTP API Jan Stancek
2022-01-27 14:04 ` Petr Vorel [this message]
2022-02-04 12:26 ` Cyril Hrubis
2022-02-04 12:39 ` 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=YfKmWdNN+G/hjphN@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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