kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]

kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]

[Михаил Гаврилов]

kernel BUG at fs/btrfs/extent-tree.c:1833!
invalid opcode: 0000 [#1] SMP
Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4
tun nls_utf8 isofs rfcomm fuse nf_conntrack_netbios_ns
nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
xt_conntrack ebtable_nat ebtable_broute bridge ebtable_filter ebtables
ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6
nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_filter
ip6_tables iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security bnep
snd_usb_audio snd_usbmidi_lib snd_rawmidi hid_logitech_hidpp btusb
btrtl btbcm btintel bluetooth gspca_zc3xx gspca_main videodev uas
media joydev usb_storage hid_logitech_dj rfkill btrfs xor intel_rapl
iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi snd_hda_codec_realtek
coretemp
 snd_hda_codec_generic snd_hda_codec_ca0132 iTCO_wdt
iTCO_vendor_support kvm_intel vfat ppdev fat kvm snd_hda_intel
snd_hda_codec snd_hda_core snd_hwdep snd_seq crct10dif_pclmul
snd_seq_device crc32_pclmul crc32c_intel snd_pcm raid6_pq snd_timer
snd mei_me mei soundcore shpchp i2c_i801 lpc_ich parport_pc
tpm_infineon parport tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace
sunrpc binfmt_misc i915 i2c_algo_bit drm_kms_helper drm 8021q garp stp
llc mrp serio_raw r8169 mii video
CPU: 7 PID: 10775 Comm: kworker/u16:15 Not tainted 4.2.6-301.fc23.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. Z87M-D3H/Z87M-D3H, BIOS
F11 08/12/2014
Workqueue: btrfs-extent-refs btrfs_extent_refs_helper [btrfs]
task: ffff8805c042bb00 ti: ffff88074d748000 task.ti: ffff88074d748000
RIP: 0010:[<ffffffffa05e9af7>]  [<ffffffffa05e9af7>]
insert_inline_extent_backref+0xe7/0xf0 [btrfs]
RSP: 0018:ffff88074d74baa8  EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff880000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff88074d74bb28 R08: 0000000000004000 R09: ffff88074d74b9a0
R10: 0000000000000000 R11: 0000000000000003 R12: ffff8807ec932800
R13: ffff88048185d090 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88081e3c0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000013dd12294020 CR3: 0000000001c0b000 CR4: 00000000001406e0
Stack:
 0000000000000000 0000000000000005 0000000000000000 0000000000000000
 0000000000000001 ffffffff81200206 ffff88074d74bb08 ffffffffa05dcd4a
 00000000000033e8 000000004e7e87f3 ffff8807ea905800 0000000000000000
Call Trace:
 [<ffffffff81200206>] ? kmem_cache_alloc+0x1d6/0x210
 [<ffffffffa05dcd4a>] ? btrfs_alloc_path+0x1a/0x20 [btrfs]
 [<ffffffffa05e9f99>] __btrfs_inc_extent_ref.isra.52+0xa9/0x270 [btrfs]
 [<ffffffffa05ef6b4>] __btrfs_run_delayed_refs+0xc84/0x1080 [btrfs]
 [<ffffffff811a5347>] ? mempool_free_slab+0x17/0x20
 [<ffffffff812001c3>] ? kmem_cache_alloc+0x193/0x210
 [<ffffffffa05f2674>] btrfs_run_delayed_refs.part.73+0x74/0x270 [btrfs]
 [<ffffffffa05f290e>] delayed_ref_async_start+0x7e/0x90 [btrfs]
 [<ffffffffa06384b2>] btrfs_scrubparity_helper+0xc2/0x260 [btrfs]
 [<ffffffffa063868e>] btrfs_extent_refs_helper+0xe/0x10 [btrfs]
 [<ffffffff810b650e>] process_one_work+0x19e/0x3f0
 [<ffffffff810b67ae>] worker_thread+0x4e/0x450
 [<ffffffff810b6760>] ? process_one_work+0x3f0/0x3f0
 [<ffffffff810bc8b8>] kthread+0xd8/0xf0
 [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160
 [<ffffffff817797df>] ret_from_fork+0x3f/0x70
 [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160
Code: 10 49 89 d9 48 8b 55 c0 4c 89 7c 24 10 4c 89 f1 4c 89 ee 4c 89
e7 89 44 24 08 48 8b 45 20 48 89 04 24 e8 5d d5 ff ff 31 c0 eb ac <0f>
0b e8 92 47 ab e0 66 90 0f 1f 44 00 00 55 48 89 e5 41 57 41
RIP  [<ffffffffa05e9af7>] insert_inline_extent_backref+0xe7/0xf0 [btrfs]
 RSP <ffff88074d74baa8>



Report from downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1287508


--
Best Regards,
Mike Gavrilov.

Re: kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]

[Filipe Manana]

On Wed, Dec 2, 2015 at 9:18 AM, Михаил Гаврилов
<mikhail.v.gavrilov@gmail.com> wrote:
> kernel BUG at fs/btrfs/extent-tree.c:1833!
> invalid opcode: 0000 [#1] SMP
> Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4
> tun nls_utf8 isofs rfcomm fuse nf_conntrack_netbios_ns
> nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
> xt_conntrack ebtable_nat ebtable_broute bridge ebtable_filter ebtables
> ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6
> nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_filter
> ip6_tables iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4
> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security bnep
> snd_usb_audio snd_usbmidi_lib snd_rawmidi hid_logitech_hidpp btusb
> btrtl btbcm btintel bluetooth gspca_zc3xx gspca_main videodev uas
> media joydev usb_storage hid_logitech_dj rfkill btrfs xor intel_rapl
> iosf_mbi x86_pkg_temp_thermal snd_hda_codec_hdmi snd_hda_codec_realtek
> coretemp
>  snd_hda_codec_generic snd_hda_codec_ca0132 iTCO_wdt
> iTCO_vendor_support kvm_intel vfat ppdev fat kvm snd_hda_intel
> snd_hda_codec snd_hda_core snd_hwdep snd_seq crct10dif_pclmul
> snd_seq_device crc32_pclmul crc32c_intel snd_pcm raid6_pq snd_timer
> snd mei_me mei soundcore shpchp i2c_i801 lpc_ich parport_pc
> tpm_infineon parport tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace
> sunrpc binfmt_misc i915 i2c_algo_bit drm_kms_helper drm 8021q garp stp
> llc mrp serio_raw r8169 mii video
> CPU: 7 PID: 10775 Comm: kworker/u16:15 Not tainted 4.2.6-301.fc23.x86_64 #1
> Hardware name: Gigabyte Technology Co., Ltd. Z87M-D3H/Z87M-D3H, BIOS
> F11 08/12/2014
> Workqueue: btrfs-extent-refs btrfs_extent_refs_helper [btrfs]
> task: ffff8805c042bb00 ti: ffff88074d748000 task.ti: ffff88074d748000
> RIP: 0010:[<ffffffffa05e9af7>]  [<ffffffffa05e9af7>]
> insert_inline_extent_backref+0xe7/0xf0 [btrfs]
> RSP: 0018:ffff88074d74baa8  EFLAGS: 00010293
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: ffff880000000000 RSI: 0000000000000001 RDI: 0000000000000000
> RBP: ffff88074d74bb28 R08: 0000000000004000 R09: ffff88074d74b9a0
> R10: 0000000000000000 R11: 0000000000000003 R12: ffff8807ec932800
> R13: ffff88048185d090 R14: 0000000000000000 R15: 0000000000000000
> FS:  0000000000000000(0000) GS:ffff88081e3c0000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000013dd12294020 CR3: 0000000001c0b000 CR4: 00000000001406e0
> Stack:
>  0000000000000000 0000000000000005 0000000000000000 0000000000000000
>  0000000000000001 ffffffff81200206 ffff88074d74bb08 ffffffffa05dcd4a
>  00000000000033e8 000000004e7e87f3 ffff8807ea905800 0000000000000000
> Call Trace:
>  [<ffffffff81200206>] ? kmem_cache_alloc+0x1d6/0x210
>  [<ffffffffa05dcd4a>] ? btrfs_alloc_path+0x1a/0x20 [btrfs]
>  [<ffffffffa05e9f99>] __btrfs_inc_extent_ref.isra.52+0xa9/0x270 [btrfs]
>  [<ffffffffa05ef6b4>] __btrfs_run_delayed_refs+0xc84/0x1080 [btrfs]
>  [<ffffffff811a5347>] ? mempool_free_slab+0x17/0x20
>  [<ffffffff812001c3>] ? kmem_cache_alloc+0x193/0x210
>  [<ffffffffa05f2674>] btrfs_run_delayed_refs.part.73+0x74/0x270 [btrfs]
>  [<ffffffffa05f290e>] delayed_ref_async_start+0x7e/0x90 [btrfs]
>  [<ffffffffa06384b2>] btrfs_scrubparity_helper+0xc2/0x260 [btrfs]
>  [<ffffffffa063868e>] btrfs_extent_refs_helper+0xe/0x10 [btrfs]
>  [<ffffffff810b650e>] process_one_work+0x19e/0x3f0
>  [<ffffffff810b67ae>] worker_thread+0x4e/0x450
>  [<ffffffff810b6760>] ? process_one_work+0x3f0/0x3f0
>  [<ffffffff810bc8b8>] kthread+0xd8/0xf0
>  [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160
>  [<ffffffff817797df>] ret_from_fork+0x3f/0x70
>  [<ffffffff810bc7e0>] ? kthread_worker_fn+0x160/0x160
> Code: 10 49 89 d9 48 8b 55 c0 4c 89 7c 24 10 4c 89 f1 4c 89 ee 4c 89
> e7 89 44 24 08 48 8b 45 20 48 89 04 24 e8 5d d5 ff ff 31 c0 eb ac <0f>
> 0b e8 92 47 ab e0 66 90 0f 1f 44 00 00 55 48 89 e5 41 57 41
> RIP  [<ffffffffa05e9af7>] insert_inline_extent_backref+0xe7/0xf0 [btrfs]
>  RSP <ffff88074d74baa8>

We got this fixed in 4.4-rc1:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b06c4bf5c874a57254b197f53ddf588e7a24a2bf

Patches were tagged for stable releases but weren't yet backported to
4.2 and 4.3 (the issue affects all 4.2 and 4.3 releases at the
moment).

cheers

>
>
>
> Report from downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1287508
>
>
> --
> Best Regards,
> Mike Gavrilov.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Filipe David Manana,

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

Re: kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]

[Gerald Hopf]

>> kernel BUG at fs/btrfs/extent-tree.c:1833!
> We got this fixed in 4.4-rc1:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b06c4bf5c874a57254b197f53ddf588e7a24a2bf
>
> Patches were tagged for stable releases but weren't yet backported to
> 4.2 and 4.3 (the issue affects all 4.2 and 4.3 releases at the
> moment).
>
> cheers
Could someone please backport this important fix and merge it into the 
stable kernels?
Today Kernel 4.2.7 and 4.3.1 were finally released and as far as I can 
see in the changelog no btrfs fixes were included in these updates.
=> still can't do balance without crashing the system

Gerald

Re: kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]

[Filipe Manana]

On Wed, Dec 9, 2015 at 11:05 PM, Gerald Hopf <gerald.hopf@nv-systems.net> wrote:
>
>>> kernel BUG at fs/btrfs/extent-tree.c:1833!
>>
>> We got this fixed in 4.4-rc1:
>>
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b06c4bf5c874a57254b197f53ddf588e7a24a2bf
>>
>> Patches were tagged for stable releases but weren't yet backported to
>> 4.2 and 4.3 (the issue affects all 4.2 and 4.3 releases at the
>> moment).
>>
>> cheers
>
> Could someone please backport this important fix and merge it into the
> stable kernels?
> Today Kernel 4.2.7 and 4.3.1 were finally released and as far as I can see
> in the changelog no btrfs fixes were included in these updates.
> => still can't do balance without crashing the system

It's up to the stable team (cc'ed) to do that. For some reason, all
patches (at least btrfs ones) tagged for stable haven't been added to
4.3.x and 4.2.x at least for quite some time. Probably just a long
queue and a busy maintainer or on vacations or something like that.

>
> Gerald
>



-- 
Filipe David Manana,

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

Re: kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]

[Greg KH]

On Wed, Dec 09, 2015 at 11:29:48PM +0000, Filipe Manana wrote:
> On Wed, Dec 9, 2015 at 11:05 PM, Gerald Hopf <gerald.hopf@nv-systems.net> wrote:
> >
> >>> kernel BUG at fs/btrfs/extent-tree.c:1833!
> >>
> >> We got this fixed in 4.4-rc1:
> >>
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b06c4bf5c874a57254b197f53ddf588e7a24a2bf
> >>
> >> Patches were tagged for stable releases but weren't yet backported to
> >> 4.2 and 4.3 (the issue affects all 4.2 and 4.3 releases at the
> >> moment).
> >>
> >> cheers
> >
> > Could someone please backport this important fix and merge it into the
> > stable kernels?
> > Today Kernel 4.2.7 and 4.3.1 were finally released and as far as I can see
> > in the changelog no btrfs fixes were included in these updates.
> > => still can't do balance without crashing the system
> 
> It's up to the stable team (cc'ed) to do that. For some reason, all
> patches (at least btrfs ones) tagged for stable haven't been added to
> 4.3.x and 4.2.x at least for quite some time. Probably just a long
> queue and a busy maintainer or on vacations or something like that.

Yes a combination of those two things.  I'm digging myself out of the
stable queue, right now there are over 10 btrfs stable patches in the
queue that I haven't even touched yet, sorry.

thanks,

greg k-h