public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Dave Chinner <david@fromorbit.com>,
	fstests@vger.kernel.org, Dave Chinner <dchinner@redhat.com>
Subject: Re: [GIT PULL] fstests: updates on 2016-08-20
Date: Tue, 23 Aug 2016 23:23:02 +0800	[thread overview]
Message-ID: <20160823152302.GN27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160823151042.GC8265@birch.djwong.org>

On Tue, Aug 23, 2016 at 08:10:43AM -0700, Darrick J. Wong wrote:
> > > Hi Eryu,
> > > 
> > > I just pulled this all in and got an unexpected surprise - this new
> > > test killed all of my test machines. From your description ("normal
> > > update") I didn't expect to see something like this occur - I pulled
> > > it, confirmed commits match, then pushed it to my test machines
> > > and started a test cycle. I expected to see it complete without any
> > > significant problems.
> > 
> > I saw only mount failures from this case in my testings (4.8-rc2
> > kernel), I didn't expect any crash either.
> 
> Is this in reference generic/323?  For whatever reason I get a flood
> of overlapping kernel stack smeared all over ttyS0.

If you're using my github tree, it should be generic/375. Dave hasn't
pushed this update to upstream tree yet, so you shouldn't see it if
you're using upstream tree.

Thanks,
Eryu

  reply	other threads:[~2016-08-23 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 14:44 [GIT PULL] fstests: updates on 2016-08-20 Eryu Guan
2016-08-23  6:54 ` Dave Chinner
2016-08-23  7:16   ` Eryu Guan
2016-08-23 15:10     ` Darrick J. Wong
2016-08-23 15:23       ` Eryu Guan [this message]
2016-08-23 22:18       ` Dave Chinner
2016-08-26  4:51 ` Dave Chinner
2016-08-26  7:13   ` Eryu Guan

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=20160823152302.GN27776@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=fstests@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