kernel call trace during send/receive

Hey.

Just got the following during send/receiving a big snapshot from one btrfs to another fresh one.

Both under kernel 4.2.6, tools 4.3

The send/receive seems to continue however...

Any ideas what that means?

Cheers,
Chris.

Nov 27 01:52:36 heisenberg kernel: ------------[ cut here ]------------
Nov 27 01:52:36 heisenberg kernel: WARNING: CPU: 7 PID: 18086 at /build/linux-CrHvZ_/linux-4.2.6/fs/btrfs/send.c:5794 btrfs_ioctl_send+0x661/0x1120 [btrfs]()
Nov 27 01:52:36 heisenberg kernel: Modules linked in: ext4 mbcache jbd2 nls_utf8 nls_cp437 vfat fat uas 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 ccm ebtable_filter ebtables seqiv ecb drbg ansi_cprng algif_skcipher md4 algif_hash af_alg binfmt_misc xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 cpufreq_userspace cpufreq_powersave cpufreq_stats cpufreq_conservative 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 ip_tables x_tables joydev rtsx_pci_ms rtsx_pci_sdmmc mmc_core memstick iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal
Nov 27 01:52:36 heisenberg kernel:  intel_powerclamp intel_rapl iosf_mbi coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul evdev deflate ctr psmouse serio_raw twofish_generic pcspkr btusb btrtl btbcm btintel bluetooth crc16 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common sg arc4 camellia_generic iwldvm mac80211 iwlwifi cfg80211 rtsx_pci rfkill camellia_aesni_avx_x86_64 snd_hda_codec_hdmi tpm_tis tpm 8250_fintek camellia_x86_64 snd_hda_codec_realtek snd_hda_codec_generic processor battery fujitsu_laptop i2c_i801 ac lpc_ich serpent_avx_x86_64 mfd_core snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm shpchp snd_timer e1000e snd soundcore i915 ptp pps_core video button drm_kms_helper drm thermal_sys mei_me
Nov 27 01:52:36 heisenberg kernel:  i2c_algo_bit mei serpent_sse2_x86_64 xts serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_avx_x86_64 cast5_generic cast_common des_generic cbc cmac xcbc rmd160 sha512_ssse3 sha512_generic sha256_ssse3 sha256_generic hmac crypto_null af_key xfrm_algo loop parport_pc ppdev lp parport autofs4 dm_crypt dm_mod md_mod btrfs xor raid6_pq uhci_hcd usb_storage sd_mod crc32c_intel aesni_intel aes_x86_64 glue_helper ahci lrw gf128mul ablk_helper libahci cryptd libata ehci_pci xhci_pci ehci_hcd scsi_mod xhci_hcd usbcore usb_common
Nov 27 01:52:36 heisenberg kernel: CPU: 7 PID: 18086 Comm: btrfs Not tainted 4.2.0-1-amd64 #1 Debian 4.2.6-1
Nov 27 01:52:36 heisenberg kernel: Hardware name: FUJITSU LIFEBOOK E782/FJNB23E, BIOS Version 1.11 05/24/2012
Nov 27 01:52:36 heisenberg kernel:  0000000000000000 ffffffffa02e6260 ffffffff8154e2f6 0000000000000000
Nov 27 01:52:36 heisenberg kernel:  ffffffff8106e5b1 ffff880235a3c42c 00007ffd3d3796c0 ffff8802f0e5c000
Nov 27 01:52:36 heisenberg kernel:  0000000000000004 ffff88010543c500 ffffffffa02d2d81 ffff88041e5ebb00
Nov 27 01:52:36 heisenberg kernel: Call Trace:
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8154e2f6>] ? dump_stack+0x40/0x50
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8106e5b1>] ? warn_slowpath_common+0x81/0xb0
Nov 27 01:52:36 heisenberg kernel:  [<ffffffffa02d2d81>] ? btrfs_ioctl_send+0x661/0x1120 [btrfs]
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8115a8c4>] ? __alloc_pages_nodemask+0x194/0x9e0
Nov 27 01:52:36 heisenberg kernel:  [<ffffffffa029bfac>] ? btrfs_ioctl+0x26c/0x2a10 [btrfs]
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff81098e5a>] ? sched_move_task+0xca/0x1d0
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff812c50ee>] ? cpumask_next_and+0x2e/0x50
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8109b7cf>] ? select_task_rq_fair+0x23f/0x5c0
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8109ef87>] ? enqueue_task_fair+0x387/0x1120
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8101c814>] ? native_sched_clock+0x24/0x80
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8101c875>] ? sched_clock+0x5/0x10
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff811cf2c3>] ? do_vfs_ioctl+0x2c3/0x4a0
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff8106d9f6>] ? _do_fork+0x146/0x3a0
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff811cf516>] ? SyS_ioctl+0x76/0x90
Nov 27 01:52:36 heisenberg kernel:  [<ffffffff81553a32>] ? system_call_fast_compare_end+0xc/0x6b
Nov 27 01:52:36 heisenberg kernel: ---[ end trace f5fa91e2672eead0 ]---

Hey.

Hmm I guess no one has any clue about that error?

Well it seems at least that an fsck over the receiving fs passes through without any error.

Cheers,
Chris.