Re: [GIT PULL] fstests: updates on 2016-08-20

[Dave Chinner <david@fromorbit.com>]

On Tue, Aug 23, 2016 at 08:10:43AM -0700, Darrick J. Wong wrote:
> On Tue, Aug 23, 2016 at 03:16:08PM +0800, Eryu Guan wrote:
> > On Tue, Aug 23, 2016 at 04:54:47PM +1000, Dave Chinner wrote:
> > > On Sat, Aug 20, 2016 at 10:44:01PM +0800, Eryu Guan wrote:
> > > > Hi Dave,
> > > > 
> > > > Can you please pull the fstests update from the location below? This is a
> > > > normal update, which contains new generic and XFS tests and other fixes.
> > > > 
> > > > Thanks,
> > > > Eryu
> > > > 
> > > > The following changes since commit c760a54061d26890be3929e4c6659bf3dc9e0c6a:
> > > > 
> > > >   src/t_immutable: allow EPERM on immutable inode (2016-08-12 11:17:34 +0800)
> > > > 
> > > > are available in the git repository at:
> > > > 
> > > >   https://github.com/guaneryu/xfstests.git for-dave
> > > > 
> > > > for you to fetch changes up to 3c75489a57518745598e239ffeec2af64400f185:
> > > > 
> > > >   common/rc: improve _require_metadata_journaling() for ext4 (2016-08-20 00:54:28 +0800)
> > > > 
> > > > ----------------------------------------------------------------
> > > > 
> > > > fstests: update on 2016-08-20
> > > > 
> > > > This update contains:
> > > > o New tests for generic and XFS
> > > > o Miscellaneous small fixes
> > > > 
> > > > ----------------------------------------------------------------
> > > > Brian Foster (1):
> > > >       generic: shutdown fs after log recovery
> > > 
> > > 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.

generic/375 is the new test that triggers unending recursive faults
across my machines. generic/323 has been modified since late 2014,
so if it's causing you problems, then it's probably a kernel
regression...

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com