From: Dave Chinner <david@fromorbit.com>
To: Xiong Zhou <xzhou@redhat.com>
Cc: linux-next@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Linux-next parallel cp workload hang
Date: Thu, 19 May 2016 09:02:31 +1000 [thread overview]
Message-ID: <20160518230231.GA26977@dastard> (raw)
In-Reply-To: <20160518141726.GY26977@dastard>
On Thu, May 19, 2016 at 12:17:26AM +1000, Dave Chinner wrote:
> Patch below should fix the deadlock.
The test has been running for several hours without failure using
this patch, so I'd say this fixes the problem...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-05-18 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 1:46 Linux-next parallel cp workload hang Xiong Zhou
2016-05-18 5:56 ` Dave Chinner
2016-05-18 8:31 ` Xiong Zhou
2016-05-18 9:54 ` Dave Chinner
2016-05-18 11:46 ` Xiong Zhou
2016-05-18 14:17 ` Dave Chinner
2016-05-18 23:02 ` Dave Chinner [this message]
2016-05-19 6:22 ` Xiong Zhou
[not found] <20160518013802.GA4679@ZX.nay.redhat.com>
2016-05-18 2:06 ` Al Viro
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=20160518230231.GA26977@dastard \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xzhou@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 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 NNTP newsgroup(s).