From: Jens Axboe <axboe@kernel.dk>
To: fio@vger.kernel.org, Vincent Fu <vincentfu@gmail.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Kookoo Gu <Zhimin.Gu@solidigm.com>,
Damien Le Moal <dlemoal@kernel.org>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
Subject: Re: [PATCH 0/2] fix assertion failure with asynchronous I/O replay
Date: Thu, 21 Mar 2024 05:58:14 -0600 [thread overview]
Message-ID: <171102229496.7206.8236287895881846054.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240321031011.4140040-1-shinichiro.kawasaki@wdc.com>
On Thu, 21 Mar 2024 12:10:09 +0900, Shin'ichiro Kawasaki wrote:
> After the commit b85c01f7e9df ("iolog.c: fix inaccurate clat when replay
> trace") in fio version 3.36, asynchronous I/O replay with log recording
> options trigger an assertion failure. The first patch in this series fixes
> it. The second patch adds a test case to confirm the fix.
>
> Shin'ichiro Kawasaki (2):
> iolog: regrow logs in iolog_delay()
> test: add the test for regrow logs with asynchronous I/O replay
>
> [...]
Applied, thanks!
[1/2] iolog: regrow logs in iolog_delay()
commit: c3c398e0701187716b6fba847fdae192e469b80b
[2/2] test: add the test for regrow logs with asynchronous I/O replay
commit: 140c58beeee44a10358a817c7699b66c5c7290f9
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-03-21 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 3:10 [PATCH 0/2] fix assertion failure with asynchronous I/O replay Shin'ichiro Kawasaki
2024-03-21 3:10 ` [PATCH 1/2] iolog: regrow logs in iolog_delay() Shin'ichiro Kawasaki
2024-03-21 3:10 ` [PATCH 2/2] test: add the test for regrow logs with asynchronous I/O replay Shin'ichiro Kawasaki
2024-03-21 11:58 ` 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=171102229496.7206.8236287895881846054.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=Dmitry.Fomichev@wdc.com \
--cc=Zhimin.Gu@solidigm.com \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=vincentfu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).