Re: [PATCH V2] xfs: Test infinite loop while searching for a free inode slot

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



On Fri, Aug 18, 2017 at 10:10:44AM +0200, Carlos Maiolino wrote:
> Hi!
> 
> > 
> > > 
> > > Although, I'm not sure if you notice, but even you hit this assert, you will
> > > not be able to unmount the filesystem.
> > > 
> > > I'm not sure now if simply disable this test on XFS_DEBUG is the best approach,
> > > hitting the bug in XFS_DEBUG is less catastrophic because it will not lockup,
> > > but will make the FS unmountable.
> > 
> > It crashed my host immediately, because I have
> > /proc/sys/kernel/panic_on_oops set to 1.
> > 
> > Anyway, an unmountable fs is as bad as a crash, they all prevent
> > subsequent tests from running. The underlying bug is fixed, we expect
> > test to pass, not crash the host or block further testings.
> > 
> 
> Do you have any suggestion about it? The test will purposely corrupt the FS,
> which will certainly trigger this assert (it's a NO-OP without XFS_DEBUG btw),
> I've already added it to dangerous group though.

I think adding a _require_no_xfs_debug helper in common/xfs and calling
it in the new test should work (please rename if you have a better
name), e.g.

_require_no_xfs_debug()
{
	if grep -q "debug 1" /proc/fs/xfs/stat; then
		_notrun "Require XFS built without CONFIG_XFS_DEBUG"
	fi
}

> > > 
> > > I'd simply disable it in XFS_DEBUG, once the bug is exactly the same as with non
> > > debug code, but with a different behavior. Not sure though if there are people
> > > running xfstests exclusively on XFS_DEBUG.
> > 
> > I believe running xfstests with XFS_DEBUG is pretty common.
> > 
> 
> The assert is triggered even before the fixed code can catch the corruption, so,
> I think if you are not comfortable with it crashing the system, unless we remove
> the assert from the code (which I believe might be done once the fix is merged),
> I'de suggest not running this test with XFS_DEBUG.

Yeah, _notrun if XFS_DEBUG is on :)

Thanks,
Eryu
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux