From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
xfs <linux-xfs@vger.kernel.org>,
djwong@kernel.org
Subject: Re: [PATCH for 4.14] xfs_copy: don't hang if /all/ the targets hit write errors
Date: Thu, 16 Nov 2017 20:48:47 -0800 [thread overview]
Message-ID: <20171117044847.GL5119@magnolia> (raw)
In-Reply-To: <20171117034509.GK5119@magnolia>
On Thu, Nov 16, 2017 at 07:45:09PM -0800, Darrick J. Wong wrote:
> On Thu, Nov 16, 2017 at 03:10:39PM -0600, Eric Sandeen wrote:
> >
> >
> > On 11/15/17 7:14 PM, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <darrick.wong@oracle.com>
> > >
> > > If xfs_copy is told to copy a filesystem and /all/ the writer threads
> > > hit an write error, there won't be any threads to unlock mainwait, which
> > > means that write_wbuf will deadlock with itself trying to lock mainwait.
> > > Therefore, if we discover that all the writer threads are dead, just
> > > bail out.
> > >
> > > Discovered by running xfs/073 with a tiny test device.
> > >
> > > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > > ---
> > > copy/xfs_copy.c | 12 ++++++++++++
> > > 1 file changed, 12 insertions(+)
> > >
> > > diff --git a/copy/xfs_copy.c b/copy/xfs_copy.c
> > > index 33e05df..fb37375 100644
> > > --- a/copy/xfs_copy.c
> > > +++ b/copy/xfs_copy.c
> > > @@ -476,6 +476,7 @@ void
> > > write_wbuf(void)
> > > {
> > > int i;
> > > + int badness = 0;
> > >
> > > /* verify target threads */
> > > for (i = 0; i < num_targets; i++)
> > > @@ -486,6 +487,17 @@ write_wbuf(void)
> > > for (i = 0; i < num_targets; i++)
> > > if (target[i].state != INACTIVE)
> > > pthread_mutex_unlock(&targ[i].wait); /* wake up */
> > > + else
> > > + badness++;
> > > +
> > > + /*
> > > + * If all the targets are inactive then there won't be any io
> > > + * threads left to release mainwait. We're screwed, so bail out.
> > > + */
> > > + if (badness == num_targets) {
> > > + check_errors();
> >
> > libxfs_umount(mp); ?
>
> Doh. v2 on its way
Hmmm. The other error bailouts don't call libxfs_umount and it hardly
matters since we're exiting anyway. The mp is a local variable to main
so we'd have to convey abort status out of write_wbuf back to main.
That's a bigger change; do you want me to pursue that instead?
--D
> --D
>
> > -Eric
> >
> > > + exit(1);
> > > + }
> > >
> > > signal_maskfunc(SIGCHLD, SIG_UNBLOCK);
> > > pthread_mutex_lock(&mainwait);
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-17 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 1:14 [PATCH for 4.14] xfs_copy: don't hang if /all/ the targets hit write errors Darrick J. Wong
2017-11-16 21:10 ` Eric Sandeen
2017-11-17 3:45 ` Darrick J. Wong
2017-11-17 4:48 ` Darrick J. Wong [this message]
2017-11-17 5:05 ` Eric Sandeen
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=20171117044847.GL5119@magnolia \
--to=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.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;
as well as URLs for NNTP newsgroup(s).