From: Jens Axboe <axboe@kernel.dk>
To: Puthikorn Voravootivat <puthik@chromium.org>
Cc: FIO List <fio@vger.kernel.org>,
Gwendal Grignou <gwendal@chromium.org>,
Grant Grundler <grundler@chromium.org>
Subject: Re: [PATCH] Fix verify_backlog start verification before finish writing
Date: Wed, 5 Feb 2014 12:35:51 -0700 [thread overview]
Message-ID: <20140205193551.GJ27534@kernel.dk> (raw)
In-Reply-To: <1391624895-9543-1-git-send-email-puthik@chromium.org>
On Wed, Feb 05 2014, Puthikorn Voravootivat wrote:
> Due to recent fix for checking rand_seed in verify phase. In write phase,
> the IO transaction will be logged before completing the actual data write.
> If verify_backlog is enabled, verification may start before all data has
> been written. This patch disable that fix if the verify_backlog is enabled.
Thanks, this looks good!
--
Jens Axboe
prev parent reply other threads:[~2014-02-05 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 18:28 [PATCH] Fix verify_backlog start verification before finish writing Puthikorn Voravootivat
2014-02-05 19:35 ` Jens Axboe [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=20140205193551.GJ27534@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=grundler@chromium.org \
--cc=gwendal@chromium.org \
--cc=puthik@chromium.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