All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [libaio PATCH] harness: add test for aio poll missed events
Date: Fri, 21 Jan 2022 11:04:17 -0500	[thread overview]
Message-ID: <x49k0etf532.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <YeoLAu++cORO5mRL@sol.localdomain> (Eric Biggers's message of "Thu, 20 Jan 2022 17:23:14 -0800")

Eric Biggers <ebiggers@kernel.org> writes:

> On Wed, Jan 05, 2022 at 08:49:43PM -0800, Eric Biggers wrote:
>> From: Eric Biggers <ebiggers@google.com>
>> 
>> Add a regression test for a recently-fixed kernel bug where aio polls
>> sometimes didn't complete even if the file is ready.
>> 
>> This is a cleaned-up version of the test which I originally posted at
>> https://lore.kernel.org/r/YbMKtAjSJdXNTzOk@sol.localdomain
>> 
>> Signed-off-by: Eric Biggers <ebiggers@google.com>
>> ---
>>  harness/cases/23.t | 255 +++++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 255 insertions(+)
>>  create mode 100644 harness/cases/23.t
>
> Jeff, any feedback on this?  It looks like you're maintaining libaio.
>
> I feel that this should go in the libaio test suite given the other aio tests
> there already (including the one for aio poll), but I'd also be glad to put this
> in LTP instead if you would prefer that.  Just let me know...

Sorry for the late reply.  I'll get this integrated.  Thanks a lot for
providing the test case!

-Jeff


  reply	other threads:[~2022-01-21 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06  4:49 [libaio PATCH] harness: add test for aio poll missed events Eric Biggers
2022-01-21  1:23 ` Eric Biggers
2022-01-21 16:04   ` Jeff Moyer [this message]
2022-01-21  7:20 ` Christoph Hellwig

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=x49k0etf532.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=ebiggers@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.