From: Jan Kara <jack@suse.cz>
To: fstests@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 1/5] More page fault stress tests and generic/038 fix
Date: Mon, 18 Apr 2016 21:32:30 +0200 [thread overview]
Message-ID: <1461007955-7921-1-git-send-email-jack@suse.cz> (raw)
Hello,
I'm sending couple of changes that I have accumulated locally. The first
patch slightly simplifies the current page fault stress test generic/340.
Another three patches add more page fault stress tests. The last patch
fixes unrelated issue with generic/038 test which didn't properly wait for
the run processes and thus occasionally umount failed with EBUSY.
Honza
next reply other threads:[~2016-04-18 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 19:32 Jan Kara [this message]
2016-04-18 19:32 ` [PATCH 1/5] generic/340: Remove second fallocate test Jan Kara
2016-04-18 19:32 ` [PATCH 2/5] generic/343: Test races between mmap and normal writes Jan Kara
2016-04-27 15:04 ` Brian Foster
2016-04-27 16:16 ` Jan Kara
2016-04-27 16:19 ` Jan Kara
2016-04-18 19:32 ` [PATCH 3/5] generic/344: Test races between mmap and normal write for prefaulted ranges Jan Kara
2016-04-18 19:32 ` [PATCH 4/5] generic/345: Test races between processes doing mmap writes Jan Kara
2016-04-18 19:32 ` [PATCH 5/5] generic/038: Avoid EBUSY errors on umount Jan Kara
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=1461007955-7921-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=fstests@vger.kernel.org \
/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