From: Davidlohr Bueso <dave@stgolabs.net>
To: linux-btrfs@vger.kernel.org
Subject: WARN splat fs/btrfs/qgroup.c
Date: Fri, 31 Mar 2017 07:51:04 -0700 [thread overview]
Message-ID: <20170331145104.GA2270@linux-80c1.suse> (raw)
Hi,
While doing a regular kernel build I triggered the following splat
on a vanilla v4.11-rc4 kernel.
[73253.814880] WARNING: CPU: 20 PID: 631 at fs/btrfs/qgroup.c:2472 btrfs_qgroup_free_refroot+0x154/0x180 [btrfs]
[73253.814880] Modules linked in: st(E) sr_mod(E) cdrom(E) nfsv3(E) nfs_acl(E) rpcsec_gss_krb5(E) auth_rpcgss(E) nfsv4(E) dns_resolver(E) nfs(E) lockd(E) grace(E) fscache(E) ebtable_filter(E) ebtables(E) ip6table_filter(E) ip6_tables(E) iptable_filter(E) ip_tables(E) x_tables(E) af_packet(E) iscsi_ibft(E) iscsi_boot_sysfs(E) msr(E) ext4(E) crc16(E) jbd2(E) mbcache(E) intel_rapl(E) sb_edac(E) edac_core(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel(E) kvm(E) irqbypass(E) crct10dif_pclmul(E) crc32_pclmul(E) igb(E) ghash_clmulni_intel(E) iTCO_wdt(E) joydev(E) pcbc(E) aesni_intel(E) ipmi_ssif(E) aes_x86_64(E) ptp(E) iTCO_vendor_support(E) crypto_simd(E) glue_helper(E) pps_core(E) lpc_ich(E) ioatdma(E) pcspkr(E) dca(E) mfd_core(E) cryptd(E) i2c_i801(E) ipmi_si(E) ipmi_devintf(E) ipmi_msghandler(E)
[73253.814893] wmi(E) shpchp(E) button(E) sunrpc(E) btrfs(E) hid_generic(E) xor(E) usbhid(E) raid6_pq(E) sd_mod(E) mgag200(E) i2c_algo_bit(E) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) ttm(E) isci(E) ehci_pci(E) ahci(E) ehci_hcd(E) libsas(E) crc32c_intel(E) scsi_transport_sas(E) libahci(E) drm(E) usbcore(E) libata(E) sg(E) dm_multipath(E) dm_mod(E) scsi_dh_rdac(E) scsi_dh_emc(E) scsi_dh_alua(E) scsi_mod(E) autofs4(E)
[73253.814901] CPU: 20 PID: 631 Comm: btrfs-transacti Tainted: G W E 4.11.0-rc4-92.11-default+ #2
[73253.814901] Hardware name: Intel Corporation SandyBridge Platform/To be filled by O.E.M., BIOS RMLCRB.86I.R1.25.D670.1303141058 03/14/2013
[73253.814902] Call Trace:
[73253.814903] dump_stack+0x63/0x87
[73253.814905] __warn+0xd1/0xf0
[73253.814906] warn_slowpath_null+0x1d/0x20
[73253.814915] btrfs_qgroup_free_refroot+0x154/0x180 [btrfs]
[73253.814923] __btrfs_run_delayed_refs.constprop.73+0x309/0x1300 [btrfs]
[73253.814932] btrfs_run_delayed_refs+0x7e/0x2e0 [btrfs]
[73253.814941] btrfs_commit_transaction+0x39/0x950 [btrfs]
[73253.814948] ? start_transaction+0xaa/0x490 [btrfs]
[73253.814956] transaction_kthread+0x18a/0x1c0 [btrfs]
[73253.814958] kthread+0x101/0x140
[73253.814965] ? btrfs_cleanup_transaction+0x4f0/0x4f0 [btrfs]
[73253.814966] ? kthread_park+0x90/0x90
[73253.814967] ret_from_fork+0x2c/0x40
Any ideas?
Thanks,
Davidlohr
next reply other threads:[~2017-03-31 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 14:51 Davidlohr Bueso [this message]
2017-04-03 0:54 ` WARN splat fs/btrfs/qgroup.c Qu Wenruo
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=20170331145104.GA2270@linux-80c1.suse \
--to=dave@stgolabs.net \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).