[RFC PATCH 0/3] fstests: check dmesg after test

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



This patchset adds dmesg check after each test.

The first patch is a backlog patch from Eric Sandeen, which adds log
message of running to dmesg.

And the second patch takes use of this log to search for dmesg log of
last test, without clearing dmesg buffer nor dumping all dmesg to a
file, which can potentially eat all free space on testing host.

The third patch adds a function to disable this dmesg check, which can
be called by tests that generate WARNINGs/etc. on purpose, so the tests
won't fail _dmesg_check. But so far I haven't found any tests that need
this function. (Some xfs tests like xfs/111 inject corruptions on
purpose and log errors to dmesg, but _dmesg_check is unable to detect
these xfs-specific failures now.)

Right now with 3.19.0-rc4+ kernel, xfs/279 and btrfs/017 fail this
check, and btrfs/017 is a known issue, xfs/279 exposes an scsi bug

http://permalink.gmane.org/gmane.linux.scsi/98063

Thanks,
Eryu

Eric Sandeen (1):
  check: log running test to dmesg

Eryu Guan (2):
  check: check dmesg log after each test
  common: add _disable_dmesg_check function

 check     | 33 +++++++++++++++++++++++++++++++++
 common/rc |  6 ++++++
 2 files changed, 39 insertions(+)

-- 
2.1.0

--
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