From: Alexander Aring <aahringo@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/5] fcntl: add more testcases
Date: Tue, 30 May 2023 16:37:02 -0400 [thread overview]
Message-ID: <20230530203707.2965684-1-aahringo@redhat.com> (raw)
Hi,
this patch series introduces more fcntl testcases which was found by
testing fcntl on a Linux gfs2 filesystem. They can also be run on
different filesystems. It was mostly compared with the default Linux
behaviour e.g. tmpfs and gfs2, it's getting usual interessting when
a filesystem implements it's own posix lock behaviour like it's the
case for gfs2.
First ltp contribution, would like to get some review.
Alexander Aring (5):
fcntl40: test for owner values on classic posix lock
fcntl41: test for owner values on OFD posix locks
fcntl42: test for F_SETLKW interruption case
fcntl43: test for identical F_SETLKW lock requests
fcntl44: test for kill child while others waiting
testcases/kernel/syscalls/fcntl/.gitignore | 10 ++
testcases/kernel/syscalls/fcntl/Makefile | 6 +
testcases/kernel/syscalls/fcntl/fcntl40.c | 188 +++++++++++++++++++++
testcases/kernel/syscalls/fcntl/fcntl41.c | 178 +++++++++++++++++++
testcases/kernel/syscalls/fcntl/fcntl42.c | 153 +++++++++++++++++
testcases/kernel/syscalls/fcntl/fcntl43.c | 140 +++++++++++++++
testcases/kernel/syscalls/fcntl/fcntl44.c | 128 ++++++++++++++
7 files changed, 803 insertions(+)
create mode 100644 testcases/kernel/syscalls/fcntl/fcntl40.c
create mode 100644 testcases/kernel/syscalls/fcntl/fcntl41.c
create mode 100644 testcases/kernel/syscalls/fcntl/fcntl42.c
create mode 100644 testcases/kernel/syscalls/fcntl/fcntl43.c
create mode 100644 testcases/kernel/syscalls/fcntl/fcntl44.c
--
2.31.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2023-05-30 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 20:37 Alexander Aring [this message]
2023-05-30 20:37 ` [LTP] [PATCH 1/5] fcntl40: test for owner values on classic posix lock Alexander Aring
2023-06-21 9:03 ` Petr Vorel
2023-06-30 19:59 ` Alexander Aring
2023-07-02 19:18 ` Petr Vorel
2023-07-05 13:23 ` Alexander Aring
2023-07-07 8:14 ` Petr Vorel
2023-07-07 12:50 ` Alexander Aring
2023-07-07 13:17 ` Petr Vorel
2023-07-02 19:19 ` Petr Vorel
2023-05-30 20:37 ` [LTP] [PATCH 2/5] fcntl41: test for owner values on OFD posix locks Alexander Aring
2023-06-21 9:38 ` Petr Vorel
2023-06-30 20:00 ` Alexander Aring
2023-05-30 20:37 ` [LTP] [PATCH 3/5] fcntl42: test for F_SETLKW interruption case Alexander Aring
2023-05-30 20:37 ` [LTP] [PATCH 4/5] fcntl43: test for identical F_SETLKW lock requests Alexander Aring
2023-05-30 20:37 ` [LTP] [PATCH 5/5] fcntl44: test for kill child while others waiting Alexander Aring
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=20230530203707.2965684-1-aahringo@redhat.com \
--to=aahringo@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