From: Benjamin LaHaise <bcrl@kvack.org>
To: Zach Brown <zab@zabbo.net>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Dave Chinner <david@fromorbit.com>,
fstests@vger.kernel.org
Subject: Re: [patch, v3] add an aio test which closes the fd before destroying the ioctx
Date: Mon, 25 Aug 2014 12:50:43 -0400 [thread overview]
Message-ID: <20140825165043.GF20070@kvack.org> (raw)
In-Reply-To: <20140821165750.GA7116@lenny.home.zabbo.net>
On Thu, Aug 21, 2014 at 09:57:50AM -0700, Zach Brown wrote:
> On Wed, Aug 20, 2014 at 07:43:19PM -0400, Jeff Moyer wrote:
> > Hi, Dave,
> >
> > Dave Chinner <david@fromorbit.com> writes:
> >
> > > IOWs, we now have two AIO+DIO tests showing the same symptoms that
> > > no other tests show. This tends to point at AIO not being fully
> > > cleaned up and completely freed by the time the processes
> > > dispatching it have exit()d. This failure generally occurs when
> > > there is other load on the system/disks backing the test VM (e.g.
> > > running xfstests in multiple VMs at the same time) so I suspect it
> > > has to do with IO completion taking a long time.
> >
> > Process exit waits for all outstanding I/O, but maybe it's an rcu thing.
>
> I thought it did too but it doesn't look like upstream exit_aio() is
> waiting for iocbs to complete.
>
> Ben, are you digging in to this? Want me to throw something together?
Something like the following should fix it. This is only lightly tested.
Does someone already have a simple test case we can add to the libaio test
suite to verify this behaviour? I'm assuming that waiting for one ioctx
at a time is sufficient and we don't need to parallelise cancellation at
exit.
-ben
--
"Thought is the essence of where you are now."
diff --git a/fs/aio.c b/fs/aio.c
index 97bc62c..c558e9a 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -732,7 +732,6 @@ static int kill_ioctx(struct mm_struct *mm, struct kioctx *ctx,
if (atomic_xchg(&ctx->dead, 1))
return -EINVAL;
-
spin_lock(&mm->ioctx_lock);
table = rcu_dereference_raw(mm->ioctx_table);
WARN_ON(ctx != table->table[ctx->id]);
@@ -792,6 +791,8 @@ void exit_aio(struct mm_struct *mm)
return;
for (i = 0; i < table->nr; ++i) {
+ struct completion requests_done =
+ COMPLETION_INITIALIZER_ONSTACK(requests_done);
struct kioctx *ctx = table->table[i];
if (!ctx)
@@ -804,7 +805,8 @@ void exit_aio(struct mm_struct *mm)
* that it needs to unmap the area, just set it to 0.
*/
ctx->mmap_size = 0;
- kill_ioctx(mm, ctx, NULL);
+ if (!kill_ioctx(mm, ctx, &requests_done))
+ wait_for_completion(&requests_done);
}
RCU_INIT_POINTER(mm->ioctx_table, NULL);
next prev parent reply other threads:[~2014-08-25 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 19:34 [patch, v3] add an aio test which closes the fd before destroying the ioctx Jeff Moyer
2014-06-26 12:55 ` Brian Foster
2014-08-20 22:57 ` Dave Chinner
2014-08-20 23:43 ` Jeff Moyer
2014-08-21 9:16 ` Dave Chinner
2014-08-21 16:57 ` Zach Brown
2014-08-25 16:50 ` Benjamin LaHaise [this message]
2014-08-25 17:55 ` Jeff Moyer
2014-08-25 23:12 ` Dave Chinner
2014-08-26 16:05 ` Jeff Moyer
2014-08-26 17:27 ` Zach Brown
2014-08-26 17:32 ` Jeff Moyer
2014-08-27 8:49 ` Dave Chinner
2014-08-27 10:08 ` Dave Chinner
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=20140825165043.GF20070@kvack.org \
--to=bcrl@kvack.org \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jmoyer@redhat.com \
--cc=zab@zabbo.net \
/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