From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: spurious call trace during send
Date: Mon, 19 Sep 2016 23:18:28 +0200 [thread overview]
Message-ID: <1474319908.10189.28.camel@scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 4580 bytes --]
Hey.
FYI:
Just got this call trace during a send/receive (with -p) between two
btrfs on 4.7.0.
Neither btrfs-send nor -receive showed an error though and seem to have
completed successfully (at least a diff of the changes implied that.
Sep 19 20:24:38 heisenberg kernel: BTRFS info (device dm-2): disk space caching is enabled
Sep 19 20:25:53 heisenberg kernel: ------------[ cut here ]------------
Sep 19 20:25:53 heisenberg kernel: WARNING: CPU: 2 PID: 24266 at /build/linux-m2Twzh/linux-4.7.2/fs/btrfs/send.c:5964 btrfs_ioctl_send+0x537/0x1260 [btrfs]
Sep 19 20:25:53 heisenberg kernel: Modules linked in: udp_diag tcp_diag inet_diag algif_skcipher af_alg uas hmac drbg ansi_cprng ctr ccm vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat xt_tcpudp tun bridge stp llc fuse ebtable_filter ebtables joydev rtsx_pci_ms rtsx_pci_sdmmc memstick mmc_core cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative iTCO_wdt iTCO_vendor_support intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel psmouse uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb pcspkr btrtl btbcm btintel bluetooth crc16 sg rtsx_pci arc4 iwldvm mac80211 iwlwifi cfg80211 rfkill snd_hda_codec_hdmi snd_hda_codec_realtek
Sep 19 20:25:53 heisenberg kernel: snd_hda_codec_generic fjes i915 tpm_tis tpm battery fujitsu_laptop ac i2c_i801 snd_hda_intel video snd_hda_codec lpc_ich mfd_core button snd_hda_core snd_hwdep drm_kms_helper snd_pcm shpchp snd_timer e1000e snd drm soundcore mei_me ptp i2c_algo_bit pps_core mei ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_policy ipt_REJECT nf_reject_ipv4 xt_comment nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport xt_conntrack nf_conntrack iptable_filter binfmt_misc loop sunrpc parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt dm_mod raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod btrfs crc32c_generic xor raid6_pq uhci_hcd usb_storage sd_mod crc32c_intel ahci libahci aesni_intel
Sep 19 20:25:53 heisenberg kernel: libata aes_x86_64 xhci_pci glue_helper lrw xhci_hcd gf128mul ablk_helper cryptd ehci_pci ehci_hcd scsi_mod evdev usbcore serio_raw usb_common
Sep 19 20:25:53 heisenberg kernel: CPU: 2 PID: 24266 Comm: btrfs Not tainted 4.7.0-1-amd64 #1 Debian 4.7.2-1
Sep 19 20:25:53 heisenberg kernel: Hardware name: FUJITSU LIFEBOOK E782/FJNB23E, BIOS Version 1.11 05/24/2012
Sep 19 20:25:53 heisenberg kernel: 0000000000000286 000000007d5ad1ff ffffffffaff16655 0000000000000000
Sep 19 20:25:53 heisenberg kernel: 0000000000000000 ffffffffafc7895e ffff8802d1ebf42c 00007fff6fcb1800
Sep 19 20:25:53 heisenberg kernel: ffff8800c15da000 0000000040489426 ffff8802d1ebf000 ffff8803da842100
Sep 19 20:25:53 heisenberg kernel: Call Trace:
Sep 19 20:25:53 heisenberg kernel: [<ffffffffaff16655>] ? dump_stack+0x5c/0x77
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafc7895e>] ? __warn+0xbe/0xe0
Sep 19 20:25:53 heisenberg kernel: [<ffffffffc043e357>] ? btrfs_ioctl_send+0x537/0x1260 [btrfs]
Sep 19 20:25:53 heisenberg kernel: [<ffffffffb009b35e>] ? intel_pstate_update_util+0x1be/0x320
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafdeb568>] ? __memcg_kmem_get_cache+0x48/0x150
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafdd68b9>] ? kmem_cache_alloc+0x149/0x560
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafca9cdb>] ? attach_task_cfs_rq+0x3b/0x70
Sep 19 20:25:53 heisenberg kernel: [<ffffffffc04074c8>] ? btrfs_ioctl+0x8f8/0x2300 [btrfs]
Sep 19 20:25:53 heisenberg kernel: [<ffffffffaff1646a>] ? cpumask_next_and+0x2a/0x40
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafcae95d>] ? enqueue_task_fair+0x5d/0x960
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafc34675>] ? sched_clock+0x5/0x10
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafca0940>] ? check_preempt_curr+0x50/0x90
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafe0840e>] ? do_vfs_ioctl+0x9e/0x5d0
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafc77c1d>] ? _do_fork+0x14d/0x3f0
Sep 19 20:25:53 heisenberg kernel: [<ffffffffafe089b4>] ? SyS_ioctl+0x74/0x80
Sep 19 20:25:53 heisenberg kernel: [<ffffffffb01d84b6>] ? system_call_fast_compare_end+0xc/0x96
Sep 19 20:25:53 heisenberg kernel: ---[ end trace b61b956fbe6451d3 ]---
Any ideas?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
reply other threads:[~2016-09-19 21:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1474319908.10189.28.camel@scientia.net \
--to=calestyo@scientia.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).