From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Monakhov Subject: FYI: one more way to run xfstest Date: Wed, 20 Mar 2013 14:06:05 +0400 Message-ID: <87txo6xu5u.fsf@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kara To: ext4 development Return-path: Received: from mail-bk0-f48.google.com ([209.85.214.48]:58823 "EHLO mail-bk0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750991Ab3CTKGJ (ORCPT ); Wed, 20 Mar 2013 06:06:09 -0400 Received: by mail-bk0-f48.google.com with SMTP id jf20so644640bkc.7 for ; Wed, 20 Mar 2013 03:06:07 -0700 (PDT) Sender: linux-ext4-owner@vger.kernel.org List-ID: Today I've run xfstest in parallel with fsfreze/fsthaw like follows # I use dmsetup {suspend,resume} which does fsfreeze/fsthaw and other # dm's speciffic stuff (which is not related in that case) (while true ;do dmsetup suspend $TEST_DEV ;dmsetup resume $TEST_DEV;done)& (while true ;do dmsetup suspend $SCRATCH_DEV ;dmsetup resume $SCRATCH_DEV;done)& # And later as usual ./check -g auto I use origin/dev (current dev HEAD): c902ed2d06a Quickly it spots a lot of traces from incorrect freeze-api state: ------------[ cut here ]------------ WARNING: at fs/ext4/ext4_jbd2.c:50 __ext4_journal_start_sb+0x132/0x240() Hardware name: Modules linked in: cpufreq_ondemand acpi_cpufreq freq_table mperf coretemp kvm_intel kvm crc32c_intel ghash_clmulni_intel microcode sg xhci_hcd button sd_mod crc_t10dif aesni_intel ablk_helper cryptd lrw aes_x86_64 xts gf128mul ahci libahci pata_acpi ata_generic dm_mirror dm_region_hash dm_log dm_mod Pid: 29760, comm: fsx Not tainted 3.8.0-rc3+ #98 Call Trace: [] warn_slowpath_common+0xad/0xf0 [] ? ext4_da_write_begin+0x277/0x4f0 [] warn_slowpath_null+0x1a/0x20 [] __ext4_journal_start_sb+0x132/0x240 [] ext4_da_write_begin+0x277/0x4f0 [] generic_perform_write+0x148/0x3c0 [] generic_file_buffered_write+0x64/0xd0 [] __generic_file_aio_write+0x4d0/0x750 [] ext4_file_dio_write+0x253/0x4e0 [] ext4_file_write+0xd1/0x190 [] do_sync_write+0xb2/0x120 [] ? rw_verify_area+0x12c/0x270 [] vfs_write+0x182/0x1f0 [] ? sysret_check+0x22/0x5d [] sys_write+0x94/0xd0 [] system_call_fastpath+0x16/0x1b ---[ end trace be4bc73619d3477b ]--- ------------[ cut here ]------------ Also it find destroyed object in the list: ------------[ cut here ]------------ WARNING: at lib/list_debug.c:62 __list_del_entry+0x1c0/0x250() Hardware name: list_del corruption. prev->next should be ffff8801fbb747c8, but was 6b6b6b6b6b6b6b6b Modules linked in: cpufreq_ondemand acpi_cpufreq freq_table mperf coretemp kvm_intel kvm crc32c_intel ghash_clmulni_intel microcode sg xhci_hcd button sd_mod crc_t10dif aesni_intel ablk_helper cryptd lrw aes_x86_64 xts gf128mul ahci libahci pata_acpi ata_generic dm_mirror dm_region_hash dm_log dm_mod Pid: 13297, comm: jbd2/dm-3-8 Tainted: G W 3.8.0-rc3+ #98 Call Trace: [] warn_slowpath_common+0xad/0xf0 [] warn_slowpath_fmt+0x46/0x50 [] ? ext4_journal_commit_callback+0x99/0xc0 [] __list_del_entry+0x1c0/0x250 [] ext4_journal_commit_callback+0x6f/0xc0 [] jbd2_journal_commit_transaction+0x23a6/0x2570 [] ? try_to_del_timer_sync+0x82/0xa0 [] ? del_timer_sync+0x91/0x1e0 [] kjournald2+0x19f/0x6a0 [] ? wake_up_bit+0x40/0x40 [] ? bit_spin_lock+0x80/0x80 [] kthread+0x10e/0x120 [] ? __init_kthread_worker+0x70/0x70 [] ret_from_fork+0x7c/0xb0 [] ? __init_kthread_worker+0x70/0x70 ---[ end trace be4bc73619d357f9 ]--- Right now I work on this issues. But I just want to let you know about this.