From: Eryu Guan <eguan@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] generic: test pagecache invalidation after direct write
Date: Wed, 22 Mar 2017 11:09:23 +0800 [thread overview]
Message-ID: <20170322030923.GB14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170321173509.GC59313@bfoster.bfoster>
On Tue, Mar 21, 2017 at 01:35:09PM -0400, Brian Foster wrote:
> On Wed, Mar 22, 2017 at 12:53:14AM +0800, Eryu Guan wrote:
> > Test if direct write invalidates pagecache correctly, so that subsequent
> > buffer read reads the correct data from disk.
> >
> > This test is inspired by LTP tests dio29, and serves as a regression
> > test for the bug found by it, see kernel commit c771c14baa33
> > ("iomap: invalidate page caches should be after iomap_dio_complete()
> > in direct write").
> >
> > The test can be easily expanded to other write/read combinations, e.g.
> > buffer write + direct read and direct write + direct read, so they are
> > also being tested.
> >
> > Signed-off-by: Eryu Guan <eguan@redhat.com>
> > ---
> > v2: Address Brian's review comments
> > - compare buffer content byte-by-byte instead of strncmp
> > - use 'pids[i]' not *(pids + 1)
> > - dump buffer content to stdout on error
> > - initialize write buffer with (i + 1)
> > - use pwrite/pread instead of lseek+write/read
> > - remove increment of unused 'ret'
> > - call fsync(fd) instead of sync()
> > - fix typos
> >
> > .gitignore | 1 +
> > src/Makefile | 3 +-
> > src/dio-invalidate-cache.c | 326 +++++++++++++++++++++++++++++++++++++++++++++
> > tests/generic/418 | 122 +++++++++++++++++
> > tests/generic/418.out | 2 +
> > tests/generic/group | 1 +
> > 6 files changed, 454 insertions(+), 1 deletion(-)
> > create mode 100644 src/dio-invalidate-cache.c
> > create mode 100755 tests/generic/418
> > create mode 100644 tests/generic/418.out
> >
> ...
> > diff --git a/src/dio-invalidate-cache.c b/src/dio-invalidate-cache.c
> > new file mode 100644
> > index 0000000..bc795f9
> > --- /dev/null
> > +++ b/src/dio-invalidate-cache.c
> > @@ -0,0 +1,326 @@
> ...
> > +static void kill_children(pid_t *pids, int nr_child)
> > +{
> > + int i;
> > + pid_t pid;
> > +
> > + for (i = 0; i < nr_child; i++) {
> > + pid = *(pids + i);
> > + if (pid == 0)
> > + continue;
> > + kill(pid, SIGTERM);
> > + }
> > + return;
>
> Still have pids pointer arithmetic above and the return is unnecessary.
> Otherwise looks Ok to me:
I applied this change and queued for next update.
diff --git a/src/dio-invalidate-cache.c b/src/dio-invalidate-cache.c
index bc795f9..4c40c87 100644
--- a/src/dio-invalidate-cache.c
+++ b/src/dio-invalidate-cache.c
@@ -73,12 +73,11 @@ static void kill_children(pid_t *pids, int nr_child)
pid_t pid;
for (i = 0; i < nr_child; i++) {
- pid = *(pids + i);
+ pid = pids[i];
if (pid == 0)
continue;
kill(pid, SIGTERM);
}
- return;
}
static int wait_children(pid_t *pids, int nr_child)
>
> Reviewed-by: Brian Foster <bfoster@redhat.com>
Thanks for the review!
Eryu
prev parent reply other threads:[~2017-03-22 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:53 [PATCH v2] generic: test pagecache invalidation after direct write Eryu Guan
2017-03-21 17:35 ` Brian Foster
2017-03-22 3:09 ` Eryu Guan [this message]
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=20170322030923.GB14226@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bfoster@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).