From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: David Sterba <dsterba@suse.com>, Josef Bacik <jbacik@fb.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>, <lkp@01.org>,
<linux-btrfs@vger.kernel.org>
Subject: Re: [lkp] [btrfs] 994cdc1331: WARNING: CPU: 0 PID: 14378 at fs/btrfs/extent-tree.c:10030 btrfs_free_block_groups+0x29b/0x420 [btrfs]
Date: Tue, 23 Aug 2016 17:31:10 +0800 [thread overview]
Message-ID: <57BC17DE.9070405@cn.fujitsu.com> (raw)
In-Reply-To: <20160823074531.GB11135@yexl-desktop>
Hi,
On 08/23/2016 03:45 PM, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 994cdc133173fd9d69eae45cd228eec21dbed080 ("btrfs: update btrfs_space_info's bytes_may_use timely")
>
> in testcase: xfstests
> with following parameters:
>
> disk: 4HDD
> fs: btrfs
> test: generic-quick1
>
>
> on test machine: 4 threads Sandy Bridge with 6G memory
>
> caused below changes:
>
>
>
> [ 110.547115] BTRFS info (device dm-0): has skinny extents
> [ 110.617734] BTRFS info (device dm-0): checking UUID tree
> [ 110.698954] ------------[ cut here ]------------
> [ 110.704891] WARNING: CPU: 0 PID: 14378 at fs/btrfs/extent-tree.c:10030 btrfs_free_block_groups+0x29b/0x420 [btrfs]
> [ 110.719052] Modules linked in: dm_flakey dm_mod rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver netconsole btrfs xor raid6_pq sg sd_mod ata_generic pata_acpi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi irqbypass eeepc_wmi crct10dif_pclmul crc32_pclmul i915 crc32c_intel asus_wmi sparse_keymap ghash_clmulni_intel rfkill ppdev snd_hda_codec_realtek drm_kms_helper syscopyarea sysfillrect sysimgblt snd_hda_codec_generic aesni_intel fb_sys_fops lrw gf128mul glue_helper ablk_helper cryptd pcspkr drm serio_raw ata_piix pata_via snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer libata snd soundcore shpchp wmi parport_pc parport tpm_infineon video
> [ 110.788309] CPU: 0 PID: 14378 Comm: umount Not tainted 4.7.0-rc6-00079-g994cdc1 #1
> [ 110.796881] Hardware name: System manufacturer System Product Name/P8H67-M PRO, BIOS 1002 04/01/2011
> [ 110.807039] 0000000000000000 ffff88019966fcf0 ffffffff8143669b 0000000000000000
> [ 110.815555] 0000000000000000 ffff88019966fd30 ffffffff8107d3fb 0000272e00000000
> [ 110.824058] ffff880199742088 ffff88007e978000 ffff880199742000 ffff880199742400
> [ 110.832559] Call Trace:
> [ 110.836013] [<ffffffff8143669b>] dump_stack+0x63/0x88
> [ 110.842146] [<ffffffff8107d3fb>] __warn+0xcb/0xf0
> [ 110.847934] [<ffffffff8107d4ed>] warn_slowpath_null+0x1d/0x20
> [ 110.854774] [<ffffffffa06091ab>] btrfs_free_block_groups+0x29b/0x420 [btrfs]
> [ 110.862920] [<ffffffffa061b160>] close_ctree+0x190/0x370 [btrfs]
> [ 110.870015] [<ffffffff8121f1e9>] ? evict_inodes+0x189/0x1a0
> [ 110.876687] [<ffffffffa05eb9c9>] btrfs_put_super+0x19/0x20 [btrfs]
> [ 110.883959] [<ffffffff81203acf>] generic_shutdown_super+0x6f/0x100
> [ 110.891228] [<ffffffff81203df2>] kill_anon_super+0x12/0x20
> [ 110.897807] [<ffffffffa05ec7a8>] btrfs_kill_super+0x18/0x110 [btrfs]
> [ 110.905250] [<ffffffff81203fa3>] deactivate_locked_super+0x43/0x70
> [ 110.912504] [<ffffffff8120448a>] deactivate_super+0x5a/0x60
> [ 110.919134] [<ffffffff8122288f>] cleanup_mnt+0x3f/0x90
> [ 110.925330] [<ffffffff81222922>] __cleanup_mnt+0x12/0x20
> [ 110.931700] [<ffffffff8109b138>] task_work_run+0x88/0xc0
> [ 110.938068] [<ffffffff81003312>] exit_to_usermode_loop+0xc2/0xd0
> [ 110.945123] [<ffffffff81003c31>] syscall_return_slowpath+0xa1/0xb0
> [ 110.952350] [<ffffffff819105fa>] entry_SYSCALL_64_fastpath+0xa2/0xa4
> [ 110.959746] ---[ end trace 58ee3d80a0e5b015 ]---
> [ 110.960290] systemd-journald[142]: Compressed data object 695 -> 516
OK, thanks for the report.
I forgot to run dm-flakey related xfstests test cases when testing this
patch, really sorry.
I'll look into this problem.
Regards,
Xiaoguang Wang
>
>
> To reproduce:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
>
>
>
> Thanks,
> Xiaolong
>
>
prev parent reply other threads:[~2016-08-23 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 7:45 [lkp] [btrfs] 994cdc1331: WARNING: CPU: 0 PID: 14378 at fs/btrfs/extent-tree.c:10030 btrfs_free_block_groups+0x29b/0x420 [btrfs] kernel test robot
2016-08-23 9:31 ` Wang Xiaoguang [this message]
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=57BC17DE.9070405@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@intel.com \
/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