From: Chris Mason <clm@fb.com>
To: Erik Berg <btrfs@slipsprogrammoer.no>
Cc: <linux-btrfs@vger.kernel.org>, Mark Fasheh <mfasheh@suse.de>
Subject: Re: Kernel crash during "btrfs device delete" on raid6 volume
Date: Tue, 4 Nov 2014 10:58:48 -0500 [thread overview]
Message-ID: <1415116728.25930.1@mail.thefacebook.com> (raw)
In-Reply-To: <1415112914.25930.0@mail.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 3529 bytes --]
On Tue, Nov 4, 2014 at 9:55 AM, Chris Mason <clm@fb.com> wrote:
> On Tue, Nov 4, 2014 at 9:36 AM, Erik Berg <btrfs@slipsprogrammoer.no>
> wrote:
>> Pulled the latest btrfs-progs from kdave (v3.17-12-gcafacda) and
>> using the latest linux release candidate (3.18.0-031800rc3-generic)
>> from canonical/ubuntu
>>
>> Trying to remove device sdb1, the kernel crashes after a minute or
>> so.
>>
>> [ 597.576827] ------------[ cut here ]------------
>> [ 597.617519] kernel BUG at /home/apw/COD/linux/mm/slub.c:3334!
>> [ 597.668145] invalid opcode: 0000 [#1] SMP
>> [ 597.704410] Modules linked in: arc4 md4 ipt_MASQUERADE
>> nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat
>> nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack
>> ipt_REJECT nf_reject_ipv4 xt_CHECKSUM iptable_mangle xt_tcpudp
>> bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables
>> ebtable_nat ebtables x_tables gpio_ich intel_rapl
>> x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm
>> crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd serio_raw
>> hpilo hpwdt 8250_fintek acpi_power_meter ie31200_edac lpc_ich
>> edac_core ipmi_si ipmi_msghandler mac_hid lp parport nls_utf8 cifs
>> fscache hid_generic usbhid hid btrfs xor raid6_pq uas usb_storage
>> tg3 ptp ahci psmouse libahci pps_core hpsa
>> [ 598.268179] CPU: 1 PID: 129 Comm: kworker/u128:3 Not tainted
>> 3.18.0-031800rc3-generic #201411022335
>> [ 598.349925] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06
>> 11/09/2013
>> [ 598.413231] Workqueue: writeback bdi_writeback_workfn
>> (flush-btrfs-2)
>> [ 598.471103] task: ffff8803f16a3c00 ti: ffff880036b70000 task.ti:
>> ffff880036b70000
>> [ 598.538393] RIP: 0010:[<ffffffff811c74fd>] [<ffffffff811c74fd>]
>> kfree+0x16d/0x170
>> [ 598.606217] RSP: 0018:ffff880036b73528 EFLAGS: 00010246
>> [ 598.653844] RAX: 01ffff0000000000 RBX: ffff880036b735c8 RCX:
>> 0000000000000000
>> [ 598.717899] RDX: ffff8803743a6010 RSI: dead000000100100 RDI:
>> ffff880036b735c8
>> [ 598.781662] RBP: ffff880036b73558 R08: 0000000000000000 R09:
>> ffffea0000dadcc0
>> [ 598.846028] R10: 0000000000000001 R11: 0000000000000010 R12:
>> ffff8803f1e09800
>> [ 598.910713] R13: ffff8803ac757d40 R14: ffffffffc04fed0c R15:
>> ffff880036b735d8
>> [ 598.975333] FS: 0000000000000000(0000) GS:ffff88040b420000(0000)
>> knlGS:0000000000000000
>> [ 599.048512] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> [ 599.100167] CR2: 00007fa9a3854024 CR3: 0000000001c16000 CR4:
>> 00000000001407e0
>> [ 599.165150] Stack:
>> [ 599.183305] ffff8803f1e09800 00000dad07c20000 ffff8803f1e09800
>> ffff8803ac757d40
>> [ 599.249603] ffff8803ac757d40 ffff880036b735d8 ffff880036b73618
>> ffffffffc04fed0c
>> [ 599.316306] ffff8803f1b86b00 ffff880374338000 00000dad07dc0000
>> ffff880036b73638
>> [ 599.383404] Call Trace:
>> [ 599.405429] [<ffffffffc04fed0c>]
>> btrfs_lookup_csums_range+0x2ac/0x4a0 [btrfs]
>
> Not a new bug unfortunately, but since it is in the error handling
> people must not be hitting it often. It's also not related to device
> replace.
>
>
> while (ret < 0 && !list_empty(&tmplist)) {
> sums = list_entry(&tmplist, struct btrfs_ordered_sum,
> list);
> list_del(&sums->list);
> kfree(sums);
> }
>
> We're trying to call kfree on the on-stack list head. I'm fixing it
> up here, thanks for posting the oops!
Fix attached, or you can wait for the next rc. Thanks.
-chris
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: btrfs.patch --]
[-- Type: text/x-patch, Size: 1253 bytes --]
>From 6e5aafb27419f32575b27ef9d6a31e5d54661aca Mon Sep 17 00:00:00 2001
From: Chris Mason <clm@fb.com>
Date: Tue, 4 Nov 2014 06:59:04 -0800
Subject: [PATCH] Btrfs: fix kfree on list_head in btrfs_lookup_csums_range
error cleanup
If we hit any errors in btrfs_lookup_csums_range, we'll loop through all
the csums we allocate and free them. But the code was using list_entry
incorrectly, and ended up trying to free the on-stack list_head instead.
This bug came from commit 0678b6185
btrfs: Don't BUG_ON kzalloc error in btrfs_lookup_csums_range()
Signed-off-by: Chris Mason <clm@fb.com>
Reported-by: Erik Berg <btrfs@slipsprogrammoer.no>
cc: stable@vger.kernel.org # 3.3 or newer
---
fs/btrfs/file-item.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/file-item.c b/fs/btrfs/file-item.c
index 783a943..84a2d18 100644
--- a/fs/btrfs/file-item.c
+++ b/fs/btrfs/file-item.c
@@ -413,7 +413,7 @@ int btrfs_lookup_csums_range(struct btrfs_root *root, u64 start, u64 end,
ret = 0;
fail:
while (ret < 0 && !list_empty(&tmplist)) {
- sums = list_entry(&tmplist, struct btrfs_ordered_sum, list);
+ sums = list_entry(tmplist.next, struct btrfs_ordered_sum, list);
list_del(&sums->list);
kfree(sums);
}
--
1.8.1
next prev parent reply other threads:[~2014-11-04 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 14:36 Kernel crash during "btrfs device delete" on raid6 volume Erik Berg
2014-11-04 14:55 ` Chris Mason
2014-11-04 15:58 ` Chris Mason [this message]
2014-11-04 23:42 ` Mark Fasheh
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=1415116728.25930.1@mail.thefacebook.com \
--to=clm@fb.com \
--cc=btrfs@slipsprogrammoer.no \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
/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