public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: Linus' tree hangs in generic/530
Date: Wed, 15 May 2019 05:41:40 -0700	[thread overview]
Message-ID: <20190515124140.GA21791@infradead.org> (raw)
In-Reply-To: <20190515120657.GA2898@bfoster>

On Wed, May 15, 2019 at 08:07:01AM -0400, Brian Foster wrote:
> Have you determined whether this is actually hung btw as opposed to
> hitting some kind of sequence with pathological performance that isn't
> typically hit during the test? I don't recall whether the older kernel
> tests I referred to above resulted in task hung warnings or not, but I
> guess it wouldn't surprise me given how long the tests seemed to take to
> complete (I eventually just killed and expunged them).

I just waited for about an hour and then gave up..

      reply	other threads:[~2019-05-15 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  6:32 Linus' tree hangs in generic/530 Christoph Hellwig
2019-05-15 12:07 ` Brian Foster
2019-05-15 12:41   ` Christoph Hellwig [this message]

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=20190515124140.GA21791@infradead.org \
    --to=hch@infradead.org \
    --cc=bfoster@redhat.com \
    --cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox