From: Dave Chinner <david@fromorbit.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [patch, v3] add an aio test which closes the fd before destroying the ioctx
Date: Thu, 21 Aug 2014 19:16:29 +1000 [thread overview]
Message-ID: <20140821091629.GZ20518@dastard> (raw)
In-Reply-To: <x49vbpmwwvc.fsf@segfault.boston.devel.redhat.com>
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.
Hmmm - __fput()?
> > Can you spend some time trying to reproduce this and getting to the
> > bottom of whatever is triggering the unmount error?
>
> I can take a look, but not until next week. Hopefully that's ok?
Yeah, that's fine. I don't have the bandwidth to look at it either
right now, so I'll just expunge the test for the meantime.
Thanks, Jeff!
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-08-21 9:17 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 [this message]
2014-08-21 16:57 ` Zach Brown
2014-08-25 16:50 ` Benjamin LaHaise
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=20140821091629.GZ20518@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jmoyer@redhat.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 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.