From: ira.weiny@intel.com
To: fstests@vger.kernel.org
Cc: john.hubbard@gmail.com, Dave Chinner <david@fromorbit.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Jan Kara <jack@suse.cz>,
Dan Williams <dan.j.williams@intel.com>,
Jeff Layton <jlayton@kernel.org>, Ira Weiny <ira.weiny@intel.com>
Subject: [PATCH V2 0/2] Add lease testing
Date: Thu, 5 Sep 2019 10:30:24 -0700 [thread overview]
Message-ID: <20190905173026.28114-1-ira.weiny@intel.com> (raw)
From: Ira Weiny <ira.weiny@intel.com>
To get to a point of developing and testing the new Lease semantics for long
term file pins[1], add a simple lease test.
Currently the following tests are performed based on the fcntl() man page.
/* 1 */"Take Read Lease",
/* 2 */"Take Write Lease",
/* 3 */"Fail Write Lease if file is open somewhere else",
/* 4 */"Fail Read Lease if opened with write permissions",
/* 5 */"Read lease gets SIGIO on write open",
/* 6 */"Write lease gets SIGIO on read open",
/* 7 */"No SIGIO is sent with read lock on read open",
/* 8 */"Read lease gets SIGIO on write open",
[1] https://lkml.org/lkml/2019/8/14/435
Ira Weiny (2):
src/leasetest: Add lease test executable
generic: Add Lease testing
src/Makefile | 2 +-
src/leasetest.c | 859 ++++++++++++++++++++++++++++++++++++++++++
tests/generic/567 | 100 +++++
tests/generic/567.out | 2 +
tests/generic/group | 1 +
5 files changed, 963 insertions(+), 1 deletion(-)
create mode 100644 src/leasetest.c
create mode 100755 tests/generic/567
create mode 100644 tests/generic/567.out
--
2.20.1
next reply other threads:[~2019-09-05 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 17:30 ira.weiny [this message]
2019-09-05 17:30 ` [PATCH V2 1/2] src/leasetest: Add lease test executable ira.weiny
2019-09-08 14:17 ` Eryu Guan
2019-09-05 17:30 ` [PATCH V2 2/2] generic: Add Lease testing ira.weiny
2019-09-08 14:33 ` Eryu Guan
2019-09-09 15:33 ` Ira Weiny
2019-09-10 2:29 ` Eryu Guan
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=20190905173026.28114-1-ira.weiny@intel.com \
--to=ira.weiny@intel.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=jlayton@kernel.org \
--cc=john.hubbard@gmail.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