From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:48808 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935020AbcKQRKh (ORCPT ); Thu, 17 Nov 2016 12:10:37 -0500 Subject: Re: btrfs btree_ctree_super fault To: Chris Cui , References: From: Chris Mason Message-ID: <18a54fb9-dadc-cbd7-6472-6b02817755dc@fb.com> Date: Thu, 17 Nov 2016 10:34:29 -0500 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 11/17/2016 12:39 AM, Chris Cui wrote: > We have just encountered the same bug on 4.9.0-rc2. Any solution now? > >> kernel BUG at fs/btrfs/ctree.c:3172! >> invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC >> CPU: 0 PID: 22702 Comm: trinity-c40 Not tainted 4.9.0-rc4-think+ #1 >> task: ffff8804ffde37c0 task.stack: ffffc90002188000 >> RIP: 0010:[] >> [] btrfs_set_item_key_safe+0x179/0x190 [btrfs] >> RSP: 0000:ffffc9000218b8a8 EFLAGS: 00010246 >> RAX: 0000000000000000 RBX: ffff8804fddcf348 RCX: 0000000000001000 >> RDX: 0000000000000000 RSI: ffffc9000218b9ce RDI: ffffc9000218b8c7 >> RBP: ffffc9000218b908 R08: 0000000000004000 R09: ffffc9000218b8c8 >> R10: 0000000000000000 R11: 0000000000000001 R12: ffffc9000218b8b6 >> R13: ffffc9000218b9ce R14: 0000000000000001 R15: ffff880480684a88 >> FS: 00007f7c7f998b40(0000) GS:ffff880507800000(0000) knlGS:0000000000000000 >> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >> CR2: 0000000000000000 CR3: 000000044f15f000 CR4: 00000000001406f0 >> DR0: 00007f4ce439d000 DR1: 0000000000000000 DR2: 0000000000000000 >> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600 >> Stack: >> ffff880501430000 d305ffffa00a2245 006c000000000002 0500000000000010 >> 6c000000000002d3 0000000000001000 000000006427eebb ffff880480684a88 >> 0000000000000000 ffff8804fddcf348 0000000000002000 0000000000000000 >> Call Trace: >> [] __btrfs_drop_extents+0xb00/0xe30 [btrfs] We're going to bash on Josef's patch and probably send it with the next merge window (queued for stable as well). https://patchwork.kernel.org/patch/9431679/ -chris